On Wed, Dec 23, 2009 at 2:01 PM, Brad Gardner <[email protected]> wrote:
> Has anyone had difficulty with wait_timeout values on MySQL and the > autoReconnect=true setting? In the mornings, our Jetspeed 2.2 portals > error > on the first attempt to access them and they provide this in the diagnostic > log: > > caused by: com.mysql.jdbc.CommunicationsException: The last packet > successfully received from the server was172150 seconds ago.The last packet > sent successfully to the server was 172150 seconds ago, which 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. > > > Problem for me, is I have autoReconnect=true on all of the database > connections configured, including the portal(I believe that is the > default). > The error is valid, the time quoted is past the timeout value, but I don't > understand why the autoReconnect property doesn't stop this from happening. > > Is there anything specific in MySQL that needs to be configured to allow > this to work? > > I don't think so. I have experienced the same thing after long periods of inactivity, but then it does recover on subsequent requests There are lots of discussions on this issue but I don't really see a definitive solution If you want to create a JIRA issue we can try to put together a formal test, and see if its something we are doing wrong, or a problem specific to MySQL Are you having the same problem with other applications using the driver, or only the portal?
