Hi,

I'm writing a 3-tier app with hibernate persistence as part of web-application on Sun Appserver behind a web service that is being consumed by a Swing client from a remote location. The web service endpoint exposes only a couple of persistence-related methods that are then delegated to a POJO interface implemented with hibernate:
-void saveObject(MyPOJO) //saveOrUpdate
-MyPOJO openObject()

Essentially I am doing session per web service call: each of these methods starts with:
session = HibernateUtil.sessionFactory.openSession();
//do db work
//ends with
finally
{
session.close();
}

I saw someone use the following to close each session as part of unit test:
session.connection().close();
session.close();

Why? Should I be doing that at the end of each web service call?

Also should I be calling something immediately prior to application undeployment?

thanks
-nikita

Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 3.05

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

The generated SQL (show_sql=true):

Debug level Hibernate log excerpt:

forget session.connection().close() , it's not needed and it closes the jdbc connection anyways. as far as undeployment, the only thing that comes to mind is sessionFactory.close() ;

Simple answer: Do not use session.connection.close.

Explanation: That will close the JDBC link itself. That means your application is getting itself involved in managing the JDBC links. That is not right. Whatever container you are running in will handle that for you. For example, Tomcat manages its own pools. If you nuke connections by yourself, that disrupts whatever Tomcat is doing. I don't know if that will actually cause failures but it will degrade the performance of Tomcat's pooling.

The only exception to this is if you have created the session by providing it with a JDBC connection, like this:



which is rarely-used. You might use that in a stand-alone application, maybe, but it's rare.

So, no, do not call session.connection.close.

To put it another way, "if you have to ask, the answer is no."