We have used Hibernate 2.0.3 for our work and found
that it's an extremely useful tool. Our clients are
very satisfied with the performance of the
application.

However we are facing one problem, I request for
suggestions. I used Hibernate with Weblogic 7.0. We
have only the following entries in
hibernate.properties file.
====================================
hibernate.connection.datasource datasourcename
hibernate.dialect
net.sf.hibernate.dialect.OracleDialect
hibernate.show_sql false
hibernate.transaction.factory_class
net.sf.hibernate.transaction.JTATransactionFactory
hibernate.transaction.manager_lookup_class
net.sf.hibernate.transaction.WeblogicTransactionManagerLookup
===================================
I have set the maximum connections in Weblogic (WL)
connection pool as 2, minimum as 1, increment as 1 and
the shrink period as 1 minute. In the hibernate class,
I have a static SessionFactory. I open a session in
each of the hibernate methods, do some iterate, save,
delete operations and flush and close the session
before returning from the method. These operations are
happening perfectly.
The problem arises when I deploy the application
repeatedly without restarting the server. Since I have
2 connections maximum in the connection pool, in the
3rd deployment, the deployment fails.
Can you help us out ?

Implement context listener to close session factory or pool (all connections ), server will fire context destroy event.
It must be better to store sesion factory as context attribute than static singleton for web application too.
http://java.sun.com/webservices/docs/1. ... lets4.html