Hi,

I'm developping a swing application that uses the same session for the whole application. So the objects from the model are always bound to a session so that retrieve bounded objects when needed. (We don't access the data by queries but by using the lazy loading, all the objects can be accessed by a root node).

The probleme I have is that when the application starts a lot of data need to be loaded. So many threads are trying to load data using the same session. As there is only one connection bounded to a session, the connection becomes the bottleneck.

Is it possible for a session to use a pool of connection so that it can be used by many threads at the same time ?

If not, does someone see how benefits from many session without loading in memory many time the same physical object (row in the database) ?

I hope my question is clear enough...

Thanks for your suggestions and advises,

Dave

Sessions are not thread-safe and should only be used by a single thread at a time. From the Session javadoc at http://www.hibernate.org/hib_docs/v3/ap ... ssion.html:



There is a wiki page talking about various strategies for "thick" applications at: http://www.hibernate.org/333.html

Don't know if that will help and I am mainly into web applications were a session-per-request pattern is a kind of standard approach.

Yes, that was very interesting. Thanks.

The link shows that the using Hibernate in a Thick-Client context brings hard-to-solve problems...

In our situation, our major concern is the loading time. If hibernate could use many connections in one session that would be perfect (we would not have to re-design the way our application deals with Hibernate).

Unfortunately it seems pretty clear that it is not possible...


Warm regards,

Dave