Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

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

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

Stopped Database reader chnl - No Suitable Driver

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

  • Stopped Database reader chnl - No Suitable Driver

    We have 3 channels using the SUN JDBC-ODBC Bridge to read data from our database and generate HL7 messages. All 3 channels worked in MIRTH 1.5, and our main channel worked, at first, after we upgraded to 1.6. (We had not yet tested the other two channels.) Now, however, all 3 channels show as 'Stopped' and 'Disconnected' on the dashboard after deployment.

    We are not totally certain of the timing, but this problem may not have started until after the first time we rebooted the host server, and MIRTH along with it.

    All of our channels which write to the same database are still functioning properly.

    I've include the pertinent portions of the System Event screen and the MIRTH log below. We are particularly perplexed by the 'No suitable driver' message, as these channels were working at one point. We have no idea what driver to look for or where to look. MIRTH seems to be perfectly suited for our HL7 venture, but only if we can keep it working. Can anyone point us in the right direction?

    From the System Events screen:

    org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query"
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:34 )
    at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
    at org.mule.providers.AbstractMessageReceiver.start(A bstractMessageReceiver.java:396)
    at org.mule.providers.AbstractConnector.registerListe ner(AbstractConnector.java:518)
    at org.mule.impl.model.AbstractModel.registerListener s(AbstractModel.java:221)
    at org.mule.impl.model.AbstractModel.start(AbstractMo del.java:353)
    at org.mule.MuleManager.start(MuleManager.java:730)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:207)
    at org.mule.config.builders.MuleXmlConfigurationBuild er.configure(MuleXmlConfigurationBuilder.java:194)
    at com.webreach.mirth.server.Mirth.startMule(Mirth.ja va:229)
    at com.webreach.mirth.server.Mirth.restartMule(Mirth. java:186)
    at com.webreach.mirth.server.Mirth.run(Mirth.java:117 )
    Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query"
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:34 )
    at org.mule.providers.AbstractConnectionStrategy.conn ect(AbstractConnectionStrategy.java:67)
    at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:353)
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:32 )
    ... 11 more
    Caused by: org.mule.providers.ConnectException: Initialisation Failure: No suitable driver
    at com.webreach.mirth.connectors.jdbc.JdbcMessageRece iver.doConnect(JdbcMessageReceiver.java:110)
    at org.mule.providers.AbstractMessageReceiver.connect (AbstractMessageReceiver.java:360)
    at org.mule.providers.SingleAttemptConnectionStrategy .doConnect(SingleAttemptConnectionStrategy.java:32 )
    ... 14 more
    Caused by: java.sql.SQLException: No suitable driver
    at java.sql.DriverManager.getConnection(DriverManager .java:545)
    at java.sql.DriverManager.getConnection(DriverManager .java:171)
    at com.webreach.mirth.connectors.jdbc.JdbcConnector.g etConnection(JdbcConnector.java:510)
    at com.webreach.mirth.connectors.jdbc.JdbcMessageRece iver.doConnect(JdbcMessageReceiver.java:108)
    ... 16 more

    {}

    From the log file:

    ERROR 2007-09-28 00:51:51,334 [Thread-0] org.mule.impl.model.seda.SedaModel: Error starting component [6d4c3be2-f9f7-4321-91a0-4d2978da32f9]
    org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query"
    ERROR 2007-09-28 00:51:51,347 [Thread-0] org.mule.impl.model.seda.SedaModel: Error starting component [82fe0b37-a9df-4dbc-bc44-ea7caa1d4788]
    org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query"
    ERROR 2007-09-28 00:51:51,357 [Thread-0] org.mule.impl.model.seda.SedaModel: Error starting component [16fc8edb-fe61-40e4-82f7-c2be13a1ecb4]
    org.mule.providers.FatalConnectException: ReconnectStrategy "org.mule.providers.SingleAttemptConnectionStrateg y" failed to reconnect receiver on endpoint "jdbc://query
Working...
X