Connection Pool Overflow..Deadlock in Weblogic 8.1

Hi All,

I am working on an Application which is deployed on a clustered environment with 3 Weblogic Application Servers. The Number of connection pools for each Server is 5, hence in total of 15 connection pools are there for the Application, and the cache size is 10.

When a particular functionality of the Application is used for 5-6 times, it throws the following error..

weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool XYZ to allocate to applications, please increase the size of the pool and retry..@MyClass.mymethod()

After investigation, it was found that all the connections were in use and there was a deadlock, no more connections to allocate.

After resetting the connections, the same thing is repeating.

When i checked in the code, all the connections have been closed in the finally block. I also monitored the connections in the console (on the local environment), and that particular method was using a max of 2 connections and they were released, soon after the page returns back.

Can somebody help me out to resolve this issue?

Thanks in advance.

Rgds,

Aakash & Raju

[1208 byte] By [skyzherea] at [2007-10-2 7:56:54]
# 1

Why would you be using a 3 box clustered server and limit yourself to only 15 connections?

You said that the connections were all in use.

That would suggest to me that you didn't actually find all the places that the connections were being used.

Or you have a code block that is using more than one connection at a time (like 5 or 10) and even though all of them are closed eventually the total number is left open during the actual processing.

jschella at 2007-7-16 21:47:13 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 2

Hi jcshell,

Thamks for replying to the problem.

Well actually the number of connections is not 15. My Application is using 15 connection pools.

Yes it is true that one of my code segments is using more than one connections(2 to be presice.). But those connections are released when the method returns as I monitored the Connection Pool from the Server Console.

Please help me to resolve this issue.

skyzherea at 2007-7-16 21:47:13 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...