Announcement

Collapse
No announcement yet.

ERROR (com.mirth.connect.connectors.jdbc.JdbcConnector:3 08): Failed to disconnect

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

  • ERROR (com.mirth.connect.connectors.jdbc.JdbcConnector:3 08): Failed to disconnect

    Configuration :

    Mirth Connect version : 2.1.0.5389
    Operating System : Windows 7 Home Premium 64-bit
    MySQL version : 5.1.36-community-log

    I am getting following error each time I deploy/redeploy the channels :

    Code:
    [2011-06-07 01:40:59,163]  ERROR (com.mirth.connect.connectors.jdbc.JdbcConnector:308): Failed to disconnect: null
    java.lang.NullPointerException
    	at com.mirth.connect.connectors.jdbc.JdbcConnector.shutdownDataSource(JdbcConnector.java:450)
    	at com.mirth.connect.connectors.jdbc.JdbcConnector.doDisconnect(JdbcConnector.java:466)
    	at org.mule.providers.AbstractConnector.disconnect(AbstractConnector.java:801)
    	at org.mule.providers.AbstractConnector.stopConnector(AbstractConnector.java:306)
    	at org.mule.providers.AbstractConnector.doDispose(AbstractConnector.java:613)
    	at org.mule.providers.AbstractConnector.dispose(AbstractConnector.java:331)
    	at org.mule.MuleManager.unregisterConnector(MuleManager.java:508)
    	at com.mirth.connect.server.controllers.MuleEngineController.unregisterConnectors(MuleEngineController.java:822)
    	at com.mirth.connect.server.controllers.MuleEngineController.unregisterChannel(MuleEngineController.java:798)
    	at com.mirth.connect.server.controllers.MuleEngineController.undeployChannels(MuleEngineController.java:284)
    	at com.mirth.connect.server.controllers.MuleEngineController.redeployAllChannels(MuleEngineController.java:298)
    	at com.mirth.connect.server.servlets.EngineServlet.doPost(EngineServlet.java:48)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:534)
    	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:475)
    	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:224)
    	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:929)
    	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:403)
    	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:184)
    	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:864)
    	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
    	at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:47)
    	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
    	at org.eclipse.jetty.server.Server.handle(Server.java:352)
    	at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:596)
    	at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1068)
    	at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:805)
    	at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218)
    	at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:426)
    	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:508)
    	at org.eclipse.jetty.io.nio.SelectChannelEndPoint.access$000(SelectChannelEndPoint.java:34)
    	at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
    	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:451)
    	at java.lang.Thread.run(Unknown Source)
    Please help..

    Thank You,
    Santhosh

  • #2
    Anyone please help..

    Comment


    • #3
      I recently received a similar error message on a channel that has a database reader (SQL Server 2008) as its source - the first 14 lines in the error message I received were identical to the error message above.

      The solution: In the SQL window, my SELECT statement started on Line 2; Line 1 was empty. I removed the blank line so that SELECT was in Line 1, and it worked.
      Craig Haddix
      Data Coordinator
      Indiana Hemophilia & Thrombosis Center

      Comment

      Working...
      X