permaculture playing cards*
The moose likes Websphere and the fly likes WAS true pool size" title="" /> Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS "minimum pool size" > true pool size" Watch "WAS "minimum pool size" > true pool size" New topic
Author

WAS "minimum pool size" > true pool size

GS Rollen
Greenhorn

Joined: May 14, 2003
Posts: 9
We have a high database transaction web application we are testing and our trying to find the best connection pool size. We set the "minimum pool size" in the WAS 4.0 connection pool setting for this JDBC resource to 10.
My understanding was that setting this value to 10 would create 10 connections and keep 10 connections alive. However, when I look at the application in action using the handy Resource Analyzer tool I don�t see anything reflecting 10 connections reserved. Some Values I see:
Total number of connections created: 6
Total number of connections destroyed: 0
Total number of connections allocated: 45186
Total number of connections returned to pool: 45186
Average Pool Size: 6.0 (Average: 4.628)
Average percent of the pool in use: 0.17
Likewise our DBA only sees 6 connections. Anybody know why I don�t see 10, or is my understanding of minimum connection pooling incorrect?
Thanks
Mahesh Chalil
Ranch Hand

Joined: Jan 24, 2002
Posts: 147
Hello
Your minimum connections will be aroung the "concurrent number of connections" using by the application. So, from ur info given, it is saying thatit had to create only 6 physical connections and connection pooling was able to pool with this available connections to fullfil the client requests.
GS Rollen
Greenhorn

Joined: May 14, 2003
Posts: 9
Originally posted by Mahesh Chalil:
Hello
Your minimum connections will be aroung the "concurrent number of connections" using by the application. So, from ur info given, it is saying thatit had to create only 6 physical connections and connection pooling was able to pool with this available connections to fullfil the client requests.

I see, what I really should have been looking at was under resource analyzer is the app server-->Thread Pools-->Web Container
Where it shows:
Average number of threads in Pool: 10.0(Average: 10)
Looking at this, it appears that the connection pool uses threads to obtain the 10 connections via 6 physcial connections.
Thanks,
GS
Mahesh Chalil
Ranch Hand

Joined: Jan 24, 2002
Posts: 147
Nice.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: WAS "minimum pool size" > true pool size
 
Similar Threads
Connection Pooling Doubt
PooledConnection maximum Limit
Resource Analyser
Many PCs with Swing app to IMQ - JMSException on createConnection=[C4000]: Packet acknowledge failed
WebSphere 4 connection pooling.