[Hibernate-devel] Hibernate and Connection Pooling

[Kononen M. <Mat...@no...>]

Hi,

I'm evaluating Hibernate. You claim that it performs well and it is very
suitable for J2EE-applications. But after I've read the documentation I
doubt it. (Maybe I have misunderstood something.)

When you need to update some data, you have to keep the Hibernate session
alive between reading from DB and modifying Java objects. Then the Hibernate
session knows what to update when it is commited. It's OK if you have only
few users in your system.

Let's consider J2EE case. The problem is that a Hibernate session reserves
one DB connection. If it is possible that your system has hundreds of
concurrent users updating the database, all connections of the connection
pool become reserved.

Or have I misunderstood something? Do I actually need to keep the Hibernate
session alive or do the sessions reserve connections for long periods at
all?


Matti Kononen
mat...@no...


P.S. I'm using Hibernate with Solid Embedded Engine. The attached Java file
covers its SQL dialect. For more info see www.solidtech.com.