Meaningless Drivel is fun!
The moose likes JDBC and Relational Databases and the fly likes Communication EXCEPTION Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Communication EXCEPTION" Watch "Communication EXCEPTION" New topic
Author

Communication EXCEPTION

pradeepkp pandeyy
Greenhorn

Joined: Dec 16, 2011
Posts: 2
please tell me how to reslove the mentioned problem even i tired what is suggested in this but its not working....please anyone give me exact solution


com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 51,300,941 milliseconds ago. The last packet sent successfully to the server was 51,300,941 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.
John Jai
Rancher

Joined: May 31, 2011
Posts: 1776
Hi Pradeep,

Welcome to the Ranch

Please TellTheDetails - Is this a core Java application code or involves Java EE?

Moderator pleas move the thread
pradeepkp pandeyy
Greenhorn

Joined: Dec 16, 2011
Posts: 2
first thank you john to taking interest on my problem ,this problem come in my J2EE application which runs on tomcat 6.0,please suggest me what should i do to remove this problem
Paul Clapham
Sheriff

Joined: Oct 14, 2005
Posts: 19723
    
  10

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.
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: Communication EXCEPTION
 
It's not a secret anymore!