Announcement

Collapse

NextGen (Mirth) Connect 3.11.0 Released!

NextGen (Mirth) Connect 3.11.0 is now available as an appliance update and on our GitHub page. This release contains improvements to licensing and the NCPDP data type. It also includes various security fixes, general bug fixes, and improvements to commercial extensions. See the release notes for the complete list of fixes and improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

WrappedException: No suitable driver

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WrappedException: No suitable driver

    What causes this error and how can it be prevented?

    ERROR-200: Filter error
    ERROR MESSAGE: Error evaluating filter
    org.mozilla.javascript.WrappedException: Wrapped java.sql.SQLException: No suitable driver (bc9ae174-c2a7-4f34-ad77-78d753ae9716#13)
    at org.mozilla.javascript.Context.throwAsScriptRuntim eEx(Context.java:1693)
    at org.mozilla.javascript.MemberBox.invoke(MemberBox. java:157)
    at org.mozilla.javascript.NativeJavaMethod.call(Nativ eJavaMethod.java:201)
    Caused by: java.sql.SQLException: No suitable driver
    at java.sql.DriverManager.getConnection(DriverManager .java:545)
    at java.sql.DriverManager.getConnection(DriverManager .java:140)
    at com.webreach.mirth.server.util.DatabaseConnection. <init>(DatabaseConnection.java:65)
    at com.webreach.mirth.server.util.DatabaseConnectionF actory.createDatabaseConnection(DatabaseConnection Factory.java:65)

  • #2
    Re:WrappedException: No suitable driver

    Found the problem by doing a diff against a working connector. An 'if' was accidentally deleted at the beginning of a filter but not it's body:

    Error:
    { [filter code] }
    return true;

    Works:
    if(true)
    { [filter code] }
    return true;


    The error message could have been a little clearer.

    Comment


    • #3
      Re:WrappedException: No suitable driver

      Found another cause of this error. A change in log4j.properties:

      Works:
      #log4j.logger.filter=DEBUG
      log4j.logger.filter=INFO

      Error:
      log4j.logger.filter=DEBUG
      #log4j.logger.filter=INFO

      Comment


      • #4
        Re:WrappedException: No suitable driver

        This also seems to cause the problem:

        Works:
        #log4j.logger.java.sql=DEBUG
        log4j.logger.java.sql=ERROR

        Error:
        log4j.logger.java.sql=DEBUG
        #log4j.logger.java.sql=ERROR


        What is really frustrating is getting rid of the problem. Backing out any changes is not good enough. Restarting Mirth is not good enough. The only way I've found to reset Mirth so the problem stops occurring is to follow these steps:

        Back changes out of log4j.properties
        Restart Mirth
        Back changes out of connector
        Disable connector
        Enable some other connector (in my case a prior version of connector I'm working on).
        Deploy all connectors
        Test other connector (not sure if this is needed)
        Disable other connector
        Enable connector where error occurred originally.
        Deploy all connectors
        Now connector will not get error when used.

        Note I've tried bypassing some of these steps but the error continues to occur. The only way I can get it to stop is to follow all steps.

        Comment


        • #5
          Re:WrappedException: No suitable driver

          What does your filter code look like?
          Chris Lang

          Comment

          Working...
          X