We are trying to perform an update, which fails due to a FK violation and is rolled back. All looks great from the Java side, but in the DB it leaves open a cursor.

When the update is successful, there is no cursor left open. We've gone through the steps of making sure all statement caching is disabled, but cannot figure this one out. The rollback statements are being issued as we step through the code.

This is all with HB 3.0.5, used with Spring 1.2.3 and WebLogic 9.0 CMT.


Any suggestions?

i think that it isn't hibernate problem (maybe database, spring or weblogic)

for test hibernate try same thing in standalone hibernate

what is your database ?

when we close transaction and session (or connection for jdbc or other client) then database have to release all client resources - it is possible that client crash random and database have to resolve this case