Recently we have integrated Hibernate into our product.
While moving our value objects to use the persistence layer of Hibernate,
We encounter the following problem.

The update operation is stuck. The query is created and the values are bound.
However the PreparedStatement is not closed (unlike in the insert method scenario) and the flush is not called.
See the code snippet below.

Session session = getHibernateSession();
session.update(myObject); <--------STUCK-------------

session.flush();
connectionMgr.commitTransaction(); < ----We manage the connection
session.close();


I attach the last log statements

It's extremely unlikely that anyone will be able to help you solve such a problem via the forum, it is waaaay too specific to your particular environment, and infrastructure, and customized txn management layer.

What you'll need to do, is simplify your code and isolate the problem. Eliminate things one by one.

Sure...so let me rephrase ...

Are you familiar with other cases where a certain operation halts
after binding the values to the query parameters? If so what were the causes ?

Thanks in advance,
Daphna

Are you REALLY sure it doesn't call flush, even implicitly inside the update() ( not sure if this ever happens ). Debug the hibernate code to see, sometimes flush gets called at unexpected times.

Anyways best guess is that you are getting a locking issue in the database. Something else may have taken a read lock or higher out on the row/page/table you are trying to update. SQLServer would exhibit this behaviour if a lock is blocking an operation.

If it is definately not hitting the db via flush() or otherwise I really don't know.