Do I need to place Hibernate.initialize() inside a transaction context? When I first asked myself, I thought it is a sure thing. The call needs to be place inside a transaction:


tx = session.beginTransaction();
session.lock(user, LockMode.NONE);
Hibernate.initialize(user.getSites());
tx.commit();
}catch (HibernateException e) {
if ( tx != null ) {
try {
tx.rollback();
} catch (HibernateException he) {
.......
}

}finally {
if (session!= null) {
try {
session.close();
} catch (HibernateException e) {
....
}
}
}


But everytime, I am getting a warning message as below,

WARN [net.sf.hibernate.impl.SessionImpl] - -
afterTransactionCompletion() was never called

If I remove the transaction and call Hibernate.initialize() directly. The WARN message never shows up. So I assume there is no need to initialize under a transaction context. Am I correct? If not, what do I need to do to make the warning message go away? I am a little bothered by that...

Thanks.
AW

This warning appears if the session detects the transaction has not terminated properly when it is garbage collected ( finalize method ). Check your transaction logic again to make sure either commit() or rollback() is called every time.

It's also possible that it is not this session causing the problem but another if there are others being opened in the same process. The garbage collection only runs when it feels like it so the finalize method containing this warning can run as soon as a session goes out of scope or several minutes later.

Hmm... The transaction logic is the same as when I use session.get(), session.find(), session.createQuery(), etc. The WARN message only appears when I use session.lock(); Hibernate.initialize().

If it is caused by other sessions, should I worry about it?