Hello fellow Hibernate Users!

Im currently in the process of rewriting an application using Spring(2.x) and Hibernate(3.x). as it is now i have a lot of DAO classes and some Service classes using the DAO's.
All DAO classes are using the HibernateDAOSuport class.

In this application performance is a great issue, and it is simply not possible to open a new session eveytime a DAO method is invoked.
At the same time there are currently no transaction management as well, as we fear this might criple our performance further.

My Question is this:
When, and how do i manage the opening and closing of Sessions in order to open as few as possible?
I have considered allowing a lot of the find queries to use the same session, but im unsure as how this would be implemented, and if this is a good way to do things.
i have also considered lettign the Service classes open the sessiones and pass them on to the DAO classes whenever such is used.

Hope someone can help me out.

Best regards.
MadsJac

hi,

I think, what you are talking about is the hibernate SessionFactory and not the session.
Getting an hibernate session should not exceed some millisecond. Building the SessionFactory is one time process when your Application is started.

There are many way to handle life cycle of a session and quite a lot of documentation (on my side, opening/closing session is delegated to JTA). If you keep your session open for a long time/man requests without cleaning it, you might have memory and performance problems.

Rgds,

The SessionFactory is injeted on load time, so it should't be a problem.
I know we are talking details here, but on peaks the system has to be able to handle about 500 executions/min and each execution requires about 50 database calls.
Thats a lot of session, and it would be nice to save some of them as performance is a real issue here