For me it seems that BorrowedConnectionProvider acts strangely. Method invoke rises exception if connection is not usable and invoking method is not "Close". but I had situation when two Session(?) had same conenction and on realease they both tryed to close this.

The problem is, before release there was invoke for method isClosed(). So if close is allowed without exception, then I think isClosed must be allowed also.

i think it would be much more reliable if line 41 would be

if ( !useable && !"isClosed".equals( method.getName() ) ) {
throw new HibernateException( "connnection proxy not usable after transaction completion" );
}

One typo is also there ("3 n-s in exception")")


Hibernate version: 3.2.6

Full stack trace of any exception that occurs:

org.hibernate.HibernateException: connnection proxy not usable after transaction completion
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:42)
at $Proxy118.isClosed(Unknown Source)
at org.hibernate.jdbc.ConnectionManager.isAutoCommit(ConnectionManager.java:189)
at org.hibernate.jdbc.ConnectionManager.isAggressiveReleaseNoTransactionCheck(ConnectionManager.java:243)
at org.hibernate.jdbc.ConnectionManager.afterTransaction(ConnectionManager.java:295)
at org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:225)
at org.hibernate.transaction.CacheSynchronization.afterCompletion(CacheSynchronization.java:85)
at weblogic.transaction.internal.ServerSCInfo.doAfterCompletion(ServerSCInfo.java:985)

I just bumped into the same problem and I agree to the solution.
Should I open an issue on Jira?

was this ever fixed?

http://opensource.atlassian.com/project ... e/HHH-1744
Doesn't seem so

We are currently trying to upgrade our Weblogic 11g application from Hibernate 2.x to Hibernate 3.5.3 and have run into this problem. I take it that since the linked defect above has not been resolved that there must be a work around or some other type of resolution. Note that this occurs in our application after several hibernate queries have been executed through the hibernate framework we wrote around it. The framework we wrote closes the connection after each query. I read on a Spring related message board that Spring had a similar problem with "closing connections too aggressively". Is that what we could be doing? Maybe we need to change our application to not close a connection and reuse it within the same transaction?

Any help or suggestions would be GREATLY appreciated!

If I remember correctly, I used load time weaving and applied an aspect on this class, intercepting calls to the close()/isClosed() methods, setting a boolean to true on close() and returning it on isClosed(). Spring was happy after that.

I hope it helps.