Re: Question about Archive Engine

["Kasemir, Kay" <kasemirk@ornl.gov>]

See MySQL documentation for setting the _server_configured_(!) value of ‘wait_timeout’, for example

http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html

Somewhat related: If the archive engine experiences an interruption in the connection to the relational database (which shouldn’t happen from timeouts, you need to change that on the server side), the archive engine will shut its end of the connection down and then attempt a re-connect the next time it tries to write.

With Oracle as the RDB, we’ve had archive engines run for more than a year. When Oracle was updated during that time, archive engines logged write errors/disconnects while Oracle was down, and then reconnected fine once Oracle recovered.  

-Kay

On May 13, 2016, at 1:11 AM, lzfneu <lzfneu@live.com> wrote:

hi,

I encounter a problem when archive engine takes the data from ioc via channel access and place the data to mysql database. Here is the details in termintor window:

...

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 65,099,938 milliseconds ago.  The last packet sent successfully to the server was 65,099,971 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.

...

It seems the connection is timeout. 

I have downloaded the mysql-connector-java-5.1.39.tar.gz, unzip it and add CLASSPATH to the mysql-connector-java-5.1.39-bin.jar in the .bashrc file. 

I am not quite familar with JAVA and my question is, according to the tips in terminal window, where to set the Connector/J connection property 'autoReconnect=true' to avoid this problem.

Any help will be appreciate and thanks in advance !

Zhefu