I adopted a project that was built on Hibernate 2.1.1 and discovered that the hibernate.properties file did not specify a connection pooling manager, after our Open JDBC connections started climbing radically on the 10g Application Server.
I found a good list of troubleshooting tips at to stop the leak. After going through the tips, I set the the following in hibernate.properties file:
This immediately took care of the situation, but before I deploy again, can anyone tell me what is handling the pooling now (since I have not specified a pooling manager), if anything?
And, what do you suggest for a pooling manager on the Oracle 10g App server.
My major concern is that there is no max set for pooling right now, since the property setting essentially disables hibernate's conneciton pooling, but does not establish anything in it's place.
Erin
Erin Quick-Laughlin
Java Developer, DBA
I found a good list of troubleshooting tips at to stop the leak. After going through the tips, I set the the following in hibernate.properties file:
Code:
hibernate.connection.pool_size=0
This immediately took care of the situation, but before I deploy again, can anyone tell me what is handling the pooling now (since I have not specified a pooling manager), if anything?
And, what do you suggest for a pooling manager on the Oracle 10g App server.
My major concern is that there is no max set for pooling right now, since the property setting essentially disables hibernate's conneciton pooling, but does not establish anything in it's place.
Erin
Erin Quick-Laughlin
Java Developer, DBA