1. Hibernate cannot recover after socket has timed out stackoverflow.comI have an application that uses Hibernate to connect to my MySQL database. I'm just having a weird problem with timeouts. Let's say that the socket timeout in MySQL's configurations is ... |
2. How can I set a timeout on a Hibernate save() call with a MySQL backend? stackoverflow.comWe ran into a problem in a large, Java, Hibernate-based system last week. Our backend MySQL database (hosted on Amazon RDS) went unresponsive for 5-10 minutes (it would still accept ... |
3. Hibernate/MySQL Timeout Issue coderanch.comYesterday i left my web application running for 9 hours without using it, then when I wanted to use it i got this exception java.net.SocketException MESSAGE: Connection reset STACKTRACE: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:113) at com.mysql.jdbc.util.ReadAheadInputStream.fill(ReadAheadInputStream.java:113) at com.mysql.jdbc.util.ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(ReadAheadInputStream.java:160) at com.mysql.jdbc.util.ReadAheadInputStream.read(ReadAheadInputStream.java:188) at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1953) at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2368) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2867) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1616) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1708) at com.mysql.jdbc.Connection.execSQL(Connection.java:3255) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1293) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1428) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at ... |
4. Exception in hibernate3 relating to timeout - Mysql forum.hibernate.orgThe last packet successfully received from the server was 54,880,316 milliseconds ago. The last packet sent successfully to the server was 54,880,317 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 ... |
5. mysql database timeouts and activity on tomcat6 forum.hibernate.orgI have been battling to get database connections stable in an application running on tomcat 6.0.26 with hibernate persistence. For testing purposes, I set mysql wait_timeout and interactive_timeout to 32s. context.xml is as follows: |
6. MySQL database timeout issue (proposed solution) forum.hibernate.orgAn issue I've seen much discussed recently and that I'm contending with is the default 8 hour timeout for stale database connections in MySQL. When MySQL drops the connections, the default connection pool and DBCP don't recover, and so you have to restart the context to get things working again. C3P0 is better in that rather than just dying, it catches ... |
7. mySQL Timeout Issues forum.hibernate.orgHi, I am using Hibernate Synchronizer with Tomcat and mySQL. Everything runs fine, unless, I leave my application unattended for more than 8 h. When I then call my application, it throws a exception as shown below. And will not start up angain, until I restart Tomcat. Obviously, mySQL cuts after a period of time (8h) the db-connection. Does somebody know ... |
8. MySQL timeout Problem forum.hibernate.orgI am having a problem which I believe is related to the wait_timeout (8 hour) setting. After 8 hours of inactivity I will get errors, typically with code "SQL Error: 0, SQLState: 08S01" and a stack trace saying hibernate has lost connection to MySQL. Seems from the forums that lots of people are having this problem. In spite of having implemented ... |
9. MySQL timeout error, autoReconnect=true forum.hibernate.orgThe last packet successfully received from the server was121823 seconds ago.The last packet sent successfully to the server was 121823 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' ... |