Hi,

I've a web app developed with Hibernate 1.2. When a user tries to log in after a long period of inactivity, I get the following exception:

java.sql.SQLException: No operations allowed after connection closed

I understand that MySql shuts off connections after 8 hours. I tried setting the DBCP validation query, and even specifying the "autoreconnect" parameter in the JDBC URL. No luck. Anyone have any ideas?



P.S. This seems to work ok in my Hibernate 2.0.2 based app. I'm reluctant to spend the effort to upgrade this older project unless I really need to, though.

Thanks, WILL

I have exactly the same problem with Hibernate 2. I'm using dbcp connection pooling:

hibernate.dbcp.ps.maxActive = 100
hibernate.dbcp.ps.maxIdle = 100
hibernate.dbcp.ps.maxWait = 120000
hibernate.dbcp.ps.whenExhaustedAction = 0
hibernate.dbcp.maxActive = 100
hibernate.dbcp.maxIdle = 10
hibernate.dbcp.maxWait = 120000
hibernate.dbcp.whenExhaustedAction = 0

with MySQL:

hibernate.connection.url = jdbc:mysql://myhost:3306/mydb?autoReconnect=true

The error happens after some time of inactivity (eg. over night):

net.sf.hibernate.JDBCException: Could not load object: Connection.close() has already been called. Invalid operation in this state.

Any ideas? Thanks.

Are you using 3.x version of mysql connector? There's a new feature added to the connector that prevents autoReconnect from working if autoCommit is set to false. That's because reconnecting when autoCommit is false can lead to a non-consistent db state.

Try adding query validation to your pooled connections: