Connection Pooling - causes Hang up the Server

[KasiMurugan Ramasamy]

Hi Friends,

We are encountering a problem in Websphere Connection Pooling.
We have set max connection as 10.

In a While loop we are calling a method which updates database. We are closing the connection in that database method at end.

 while(somelogic){
        methoda();
     }
     void methoda(){
      try{
       getConnection(); (from pool)
       some logic
      }finally{
        closeConnection();// we are thinking that connection goes to pool.
      }
     }
     

If the while exceeds 10 iteration, we are facing the server hang up. It seems the close connection doesn't return connection immediately to the connection pool.

Please tell me, what could be the problem?. Is there any setting we have to change.

[Joe Matthew]

I cannot be but sceptical about this code. Why do you want 10 connections? There is no guarantee that you will be taking only 10 connections or that when you close the connection, it would go back to the pool.

The question I have is whether you really require to open the connection in the called function. Open one connection for all your transactions and one you are done with it, close it. To effectively utilize the pooling of the App Server, you will be needed to code within its limits.

You can definitley increase the connections from 10 to how many you want. But that will not solve this problem.

No solution, but redesign!