I am using Hibernate to connect to a Postgres DB on Windows. I am using optimistic locking in my app, but there is one object for which I need pessimistic locking. I am trying to use the code below:



I thought that the session.lock() would throw an exception if the persistent object was already locked. But when I run my tests, the calls to session.lock() wait until the other code thread commits the transaction that got the original lock on the object.
Any clue to what I might be doing wrong, or what I'm misunderstanding?

Thanks,

BTW - I see the same results using MsSQL as the DB - the session.lock() with UPGRADE_NOWAIT call waits until the transaction that originally locked the object completes. As I said, my understanding of that lock mode is that it should throw and exception if the object has been locked by a separate transaction.