wood burning stoves*
The moose likes JDBC and the fly likes DbConnectionBroker connection pool issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "DbConnectionBroker connection pool issue" Watch "DbConnectionBroker connection pool issue" New topic
Author

DbConnectionBroker connection pool issue

SenthilKumar Natarajan
Greenhorn

Joined: Mar 21, 2001
Posts: 15
We have developed an application with the following architecture.

1) Windows NT 4.0 and Windows XP
2) Oracle 8.0
3) JDK 1.3.1_01 (Standard Edition), JSP, Servlet, Java IDL (CORBA).
4) Apache Web Server 1.3.20
5) Tomcat 3.2.2
6) DbConnectionBroker for connection pool
7) Thin Driver
8) Proprietary Application Server

(DbConnectionBroker is a pure Java package for handling multiple concurrent database connections. DbConnectionBroker creates a broker with a very simple interface for handing out and returning database connections from a configurable pool of connections. The Broker creates a dynamic pool of connections and manages them for you with a background housekeeping thread.)

In this application we are using two connection pools. Application server creates first connection pool for main application and Tomcat creates second connection pool for Store Front at the time of first access of the Store Front.

In the above architecture the application running properly.


Now we have a plan of upgrading Apache Web Server, Tomcat and JDK in the architecture as follows,

1) JDK 1.4(Standard Edition), JSP, Servlet, Java IDL (CORBA).
2) Apache Web Server 2.0
3) Tomcat 5.0

And others are same.

In the above new setup main application is working fine without accessing Store Front. At the same time, if we try to access Store Front also works fine. Problem occurs when we try to access main application again.

Now we are facing a problem in getting connection from connection pool. The problem is occurred in DbConnectionBroker. The error is

-----> Connections Exhausted! Will wait and try again in loop 1
-----> Connections Exhausted! Will wait and try again in loop 1
-----> Connections Exhausted! Will wait and try again in loop 1
-----> Connections Exhausted! Will wait and try again in loop 1
-----> Connections Exhausted! Will wait and try again in loop 2
-----> Connections Exhausted! Will wait and try again in loop 2
-----> Connections Exhausted! Will wait and try again in loop 3
-----> Connections Exhausted! Will wait and try again in loop 3
-----> Connections Exhausted! Will wait and try again in loop 4

We are closing the statements and freeing the connection.

Would any one have solutions / suggestions to help on this?

Thanks,
-Senthil
Roger Chung-Wee
Ranch Hand

Joined: Sep 29, 2002
Posts: 1683
The poolMaxConnections value is probably set to 10. See what happens if you double to value to 20.


SCJP 1.4, SCWCD 1.3, SCBCD 1.3
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: DbConnectionBroker connection pool issue
 
Similar Threads
Setting pool size in DBCP for connection pooling?
DBCP connection pool exhausted for OpenJPA
a question about connection pooling
Transaction time out problem on WAS 5.1.1
Connection Issue