I'm using spring, hibernate 3.1 and mysql 5.1.

I'm working with some legacy code that does some pretty bad coding. Here is what's happening:

This uses open session in view filter from Spring.

handleRequest() {

// This is marked transactional propagation_required using spring AOP
manager.updateObject(objA);

objA.setAddress(...);

// This is the stupid part
use remote call to invoke another thread to do some processing on objA.
blocks until the remote call finishes
}

so that other thread loads objA, writes to it, and I got a cannotacquirelockexception.

So my question is: does the hibernate session in my original call actually hold a lock to objA so that my second transaction cannot acquire the lock? I can't find anything about this in the docs or on google, and I don't understand how the session can hold a lock if it's not in a transaction.

If it is actually holding a lock on objA, how would I be able to release it? Do I do a session.flush() right before i do the remote call?

Please help. I'm a hibernate noob and this is making me very confused. Thanks so much.

It's just a wild guess, but I would try to flush the session like you suggested it yourselfe.

If flush does not work then may be you can try a session.evict(objA)

I tried both flush and evict, neither works.

Does hibernate actually hold locks to database objects outside of a database transaction?

Are you sure were talking about a db lock here and not some threading lock? Because im out of ideas. At least with the available code here.

Yes I think you should probably post the code and atleast the stack trace