Forums Register Login

Closed connnections not returning to pool

+Pie Number of slices to send: Send
Hi everyone,

I wrote a simple test program to check if the closed connections are returned to POOL. I am using websphere 5.1.1.3. In one of the classes I am opening 20 connections, and immediately closing 19 connections and doing some processing with one connection to read data from DB2 and wait for 10 mins (using wait(600000)). I set pool param to be: 'Unused timeout=180 secs', max connections=25, min connections=1, Aged time out=0....Note that I am using Data Source to get the connections. Everything is working fine except that the connections are not released until wait time is finished (i.e. 10 mins or 600000 milli secs). Alos note that I set the reaptime as 18 secs (it is too low but for testing I used this). I am using Tivoli performance viewer to monitor the connection i the pool and DB2. I use this class (servlet) and start from a browser.

Help me if there is anything I am doing wrong. Thanks...
+Pie Number of slices to send: Send
Inder,
Welcome to JavaRanch!

Are you expecting the connections to be put back in the pool or removed from the pool?
+Pie Number of slices to send: Send
hi,

I am expecting the connections to be returned to the pool as I closed the connection using conn.close() method. Later these connections may be removed from pool based on unused timeout setting in websphere. But these are never returned to the pool until my wait time of 10 mins elapses in spite of closing the connections within few secs of opening.How do I know these were not returned to pool? I am using Tivoli performnce viewer(TPW). I see these are returned to pool just after wait time and I see that in TPW. It is strange.
What is that? Is that a mongol hoarde? Can we fend them off with this tiny ad?
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 702 times.
Similar Threads
Configuring JMS Managed Connections
connection pooling problem
setQuerytimeout in CallableStatement not working. Kindly please help
database connection pooling confusion
SQL's Execution from Springs taking long time.
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 08:07:19.