Hello,

I have a mid-sized webapp (MVC with Servlets and Jsps).

I used to create a new Hibernate session for each request (sometimes several per request) and close them as soon as I was done with the work for this particular session.

Since this can not be good for performance, I was thinking about 2 other ways to handle the Session.

- Put it in the global Application-Scope
- Put it in the Http-Session-Scope

Is there any general advice on when to create a new session in MVC webapps ? The per-request way certainly is overkill, and in my quest for performance, I want to change this.

Best regards,
Yves

I would say that you are doing the correct thing already with a session-per-request pattern. This is the recommended approach and sessions are cheap enough to create. You don't say what kind of performance problems you are experiencing but I would expect that there are other (and better) ways to solve them.

An Application-scoped session will not work since a session is not thread-safe.

A Http-Session-scoped session can be used, but only for a limited time. For example, when going through a wizard-like process that is expected to be completed in a relatively short time-frame (session-per-conversation pattern). Keeping the session around longer is likely to result in problems with stale data in the session cache.

Hey nordborg,

thanks for your explanations. I will just stay with the session-per-request pattern.

Best regards,
Yves