web stats
Tracking down post-process SQL error - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Thread Tools Display Modes
Old 01-21-2015, 07:38 AM
KJB KJB is offline
Mirth Newb
Join Date: Dec 2010
Posts: 10
KJB is on a distinguished road
Default Tracking down post-process SQL error

I'm cleaning up all our channels after upgrading from 2.x.y to 3.1.1. I've cleaned up all of my depreciated warnings, and generally tightened up my code, but I'm getting this error on all my instances and can't figure out where to look for it. There isn't any indication that I can see of which channel is generating this. I'm assuming this comes from some of my sources in my channels that have database readers. They run and sql, create the message, and then run a post process sql to flag the record as processed. I'm not seeing duplicate messages or any other indication that the post processing isn't completing, just the constant stream of errors in my server log.

2015-01-21 15:21:35,707] ERROR (com.mirth.connect.connectors.jdbc.DatabaseReceive rQuery:253): An error occurred while executing the post-process SQL, retrying
com.mysql.jdbc.exceptions.jdbc4.CommunicationsExce ption: The last packet successfully received from the server was 67,228,260 milliseconds ago. The last packet sent successfully to the server was 67,228,265 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 sun.reflect.GeneratedConstructorAccessor44.newInst ance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newI nstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Construc tor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:40 8)
at com.mysql.jdbc.SQLError.createCommunicationsExcept ion(SQLError.java:1137)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3965)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:25 78)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java :2758)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionIm pl.java:2826)
at com.mysql.jdbc.PreparedStatement.executeInternal(P reparedStatement.java:2082)
at com.mysql.jdbc.PreparedStatement.execute(PreparedS tatement.java:1302)
at com.mirth.connect.connectors.jdbc.DatabaseReceiver Query.runUpdateStatement(DatabaseReceiverQuery.jav a:243)
at com.mirth.connect.connectors.jdbc.DatabaseReceiver Query.runPostProcess(DatabaseReceiverQuery.java:19 9)
at com.mirth.connect.connectors.jdbc.DatabaseReceiver .processRecord(DatabaseReceiver.java:208)
at com.mirth.connect.connectors.jdbc.DatabaseReceiver .processResultSet(DatabaseReceiver.java:160)
at com.mirth.connect.connectors.jdbc.DatabaseReceiver .poll(DatabaseReceiver.java:117)
at com.mirth.connect.donkey.server.channel.PollConnec tor$PollConnectorTask.run(PollConnector.java:131)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutp utStream.java:113)
at java.net.SocketOutputStream.write(SocketOutputStre am.java:159)
at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:140)
at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:3946)
... 13 more

Mirth connecting to mysql. Running on ubuntu linux 12.04
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -8. The time now is 01:17 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation