EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Question about Archive Engine
From: "Kasemir, Kay" <[email protected]>
To: lzfneu <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Fri, 13 May 2016 12:35:48 +0000
See MySQL documentation for setting the _server_configured_(!) value of ‘wait_timeout’, for example

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 <[email protected]> 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

References:
Question about Archive Engine lzfneu
Navigate by Date:
Prev: Re: generalTime time provider consternation Michael Westfall
Next: Re: Micronix MMC-200 motor controller Kevin Peterson
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Question about Archive Engine lzfneu
Next: Micronix MMC-200 motor controller 김지화(빔라인장치팀)
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·