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

JDBC Connection Error

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

  • JDBC Connection Error

    Hello:

    I am having an issue creating a channel that has a SQL Server Database as the source and File Writer as a connector. I know the URL I have is valid but I get the following error when the channel attempts to start. Can someone help?


    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.startComponent(A bstractModel.java:429)
    at org.mule.management.mbeans.ModelService.startCompo nent(ModelService.java:50)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.sun.jmx.mbeanserver.StandardMBeanIntrospector. invokeM2(Unknown Source)
    at com.sun.jmx.mbeanserver.StandardMBeanIntrospector. invokeM2(Unknown Source)
    at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM( Unknown Source)
    at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknow n Source)
    at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknow n Source)
    at com.sun.jmx.interceptor.DefaultMBeanServerIntercep tor.invoke(Unknown Source)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unkn own Source)
    at javax.management.remote.rmi.RMIConnectionImpl.doOp eration(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl.acce ss$200(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl$Priv ilegedOperation.run(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl.doPr ivilegedOperation(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl.invo ke(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
    at sun.rmi.transport.Transport$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Unknown Source)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages( Unknown Source)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandl er.run0(Unknown Source)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandl er.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run Task(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run (Unknown Source)
    at java.lang.Thread.run(Unknown Source)
    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 )
    ... 36 more
    Caused by: org.mule.providers.ConnectException: Initialisation Failure: No suitable driver found for 192.168.11.10
    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 )
    ... 39 more
    Caused by: java.sql.SQLException: No suitable driver found for 192.168.11.10
    at java.sql.DriverManager.getConnection(Unknown Source)
    at java.sql.DriverManager.getConnection(Unknown Source)
    at com.webreach.mirth.connectors.jdbc.JdbcConnector.g etConnection(JdbcConnector.java:510)
    at com.webreach.mirth.connectors.jdbc.JdbcMessageRece iver.doConnect(JdbcMessageReceiver.java:108)
    ... 41 more

    {}

  • #2
    Re:JDBC Connection Error

    I got this to work. I needed to specify a JDBC connection string. Sorry for any inconvencience.

    Comment

    Working...
    X