File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes connection pool properties Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "connection pool properties" Watch "connection pool properties" New topic

connection pool properties

Kathy Brodeur

Joined: May 02, 2005
Posts: 7
I have a web application that has potential to be used by about 250-300 people simultaneously. What do you suggest setting the Maximum Connections property in WAS6.0?
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper

Joined: Aug 26, 2006
Posts: 4968

Why not set it to 250-300? That way you'll always have enough connections.

Okay, that's a snide answer. But seriously, why even worry about setting an upper limit?

Well, the answer has less to do with your users, and more do do with workload and througput. The real question is, how much can your database handle. If you database can handle 300 connections, put it to 300. Does performance degrate before or after 300? When do wait times become unacceptable. Does that happen after 10 connections or after 30 connections?

My idea about connection pools is that I limit them to the point where creating the nth one no longer brings any performance gain. After that point, you either limit the number of connections, or increase your database capacity.

What about licenses? Are you capped by licenses?

These are all some of the redirects I'm trying to give you to avoid the entire topic.

Here's a little something on my website that provides more information about configuring a WebSphere 5 or 6.1 connection pool or datasource:


RoshaniG Gopal
Ranch Hand

Joined: May 15, 2006
Posts: 180
Hi Kathy,

If 300 is number of concurrent users, then the number of connections should be 300, so that all users should be able to access the application. But if the number of users (300) are total users then the number of connections should be less. If excessive connctions are maintianed by the server, performance would be an issue..
Check out the following link for more information and further pointers.


Regards,<br />Roshani
Kathy Brodeur

Joined: May 02, 2005
Posts: 7
thanks everyone- this information helps me. I just wanted to get an idea....I wasn't sure if 200 connections would be ridiculous or not. thanks for your input.
I agree. Here's the link:
subject: connection pool properties
It's not a secret anymore!