web stats
Mirth Community - View Single Post - com.mirth.connect.server.controllers.DefaultChanne lController:Error refreshing channe
View Single Post
  #1  
Old 10-07-2014, 03:18 PM
rohit.chawla12 rohit.chawla12 is offline
OBX.2 Kenobi
 
Join Date: Oct 2013
Location: Australia
Posts: 72
rohit.chawla12 is on a distinguished road
Smile com.mirth.connect.server.controllers.DefaultChanne lController:Error refreshing channe

Hi Guys,
I have the following error(PersistenceException) logs in my logs/mirth.log file which is located in the MIRTH_HOME directory. I am using Mirth 3.0.1 version. And mySql 5.6.14. I am not sure whether it's mirth or mySql issue. Please suggest.

ERROR 2014-10-01 09:01:46,230 [qtp280726080-36] com.mirth.connect.server.controllers.DefaultChanne lController: Error refreshing channel cache
com.mirth.connect.server.controllers.ControllerExc eption: org.apache.ibatis.exceptions.PersistenceException:
### Error querying database. Cause: org.apache.ibatis.transaction.TransactionException : Error configuring AutoCommit. Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: false. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsExce ption: The last packet successfully received from the server was 62,318,009 milliseconds ago. The last packet sent successfully to the server was 62,318,009 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
### The error may exist in mysql/mysql-channel.xml
### The error may involve Channel.getChannelRevision
### The error occurred while executing a query
### Cause: org.apache.ibatis.transaction.TransactionException : Error configuring AutoCommit. Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: false. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsExce ption: The last packet successfully received from the server was 62,318,009 milliseconds ago. The last packet sent successfully to the server was 62,318,009 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
at com.mirth.connect.server.controllers.DefaultChanne lController.getChannelRevisions(DefaultChannelCont roller.java:331)
at com.mirth.connect.server.controllers.DefaultChanne lController$ChannelCache.refreshCache(DefaultChann elController.java:416)
at com.mirth.connect.server.controllers.DefaultChanne lController$ChannelCache.getAllChannels(DefaultCha nnelController.java:481)
at com.mirth.connect.server.controllers.DefaultChanne lController$ChannelCache.access$200(DefaultChannel Controller.java:408)
at com.mirth.connect.server.controllers.DefaultChanne lController.getChannels(DefaultChannelController.j ava:64)
at com.mirth.connect.server.controllers.DefaultChanne lController.getChannelTags(DefaultChannelControlle r.java:176)
at com.mirth.connect.server.servlets.ChannelServlet.d oPost(ChannelServlet.java:124)
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(Ser vletHolder.java:652)
at org.eclipse.jetty.servlet.ServletHandler.doHandle( ServletHandler.java:447)
at org.eclipse.jetty.server.session.SessionHandler.do Handle(SessionHandler.java:225)
at org.eclipse.jetty.server.handler.ContextHandler.do Handle(ContextHandler.java:1038)
at org.eclipse.jetty.servlet.ServletHandler.doScope(S ervletHandler.java:374)
at org.eclipse.jetty.server.session.SessionHandler.do Scope(SessionHandler.java:189)
at org.eclipse.jetty.server.handler.ContextHandler.do Scope(ContextHandler.java:972)
at org.eclipse.jetty.server.handler.ScopedHandler.han dle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerList.handl e(HandlerList.java:52)
at org.eclipse.jetty.server.handler.HandlerWrapper.ha ndle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java :363)
at org.eclipse.jetty.server.AbstractHttpConnection.ha ndleRequest(AbstractHttpConnection.java:483)
at org.eclipse.jetty.server.AbstractHttpConnection.co ntent(AbstractHttpConnection.java:931)
at org.eclipse.jetty.server.AbstractHttpConnection$Re questHandler.content(AbstractHttpConnection.java:9 92)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpPa rser.java:856)
at org.eclipse.jetty.http.HttpParser.parseAvailable(H ttpParser.java:240)
at org.eclipse.jetty.server.AsyncHttpConnection.handl e(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SslConnection.handle(SslC onnection.java:196)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.han dle(SelectChannelEndPoint.java:627)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.r un(SelectChannelEndPoint.java:51)
at org.eclipse.jetty.util.thread.QueuedThreadPool.run Job(QueuedThreadPool.java:608)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.r un(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:744)

Thanks & Regards,
Rohit Chawla
Reply With Quote