I have a JSF web app with Hibernate 3.1. The session-per-request pattern is set up by having "current_session_context_class" set to "thread" in hibernate.cfg.xml. The database connections are obtained from a connection pool configured in the application server (Sun Application Server PE 8.2).

I can do r/w operations obtaining the session from HibernateUtil.getCurrentSession(). However, if after commit I do a Hibernate.getCurrentSession(), the operation (newSession == lastSession), where lastSession is a reference to the previous session, returns false. I can conclude that the new session is different from the new session.

From Hibernate docs I've understood that, given the thread-bound session, the second call to getCurrentSession() should return the same session. The observed behaviour is wrong or do I have a problem in the hibernate config? Using the newly obtaned session will fall into the session-per-operation anti-pattern?

I'll appreciate your orientation.
Thank you in advance.
Antonio-

To be more precise:

- Calling HibernateUtil.getCurrentSession() many times before commit() returns the same session.
- Calling HibernateUtil.getCurrentSession() after commit() returns a new session and lastSession.closed == true, of course, unless I'm incorrectly comparing both session objects.

I presume this is the correct behaviour.

Thank you.

Im not sure where you saw the above, this is also from the hibernate docs


I have not tried this, but can you set the auto_close_session value to be false, so that the session is not closed at the end of a commit/rollback? That way, you could have the session maintained as a session-per-request pattern, but its your responsibility to close it after the thread has completed?