This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes BEA/Weblogic and the fly likes Maximum Number of connections in Connection Pool. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Maximum Number of connections in Connection Pool." Watch "Maximum Number of connections in Connection Pool." New topic
Author

Maximum Number of connections in Connection Pool.

Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234

Hi ,

I have created a DataSource Service with name 'MyDataSource' in Weblogic 10 server and on to the connection pool for it , i have set a Max Capacity of 800.
Default it is 15 and i changed it to 800.

I am having a query here , If i provide a maximum number in Max Count , will it improve the performance ??

Please tell me what is the best value i need to provide here ??


Save India From Corruption - Anna Hazare.
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6661
    
    5

Quite the opposite. If your application asks for more connections or there is a connection leak, your data source will fail. The theoretical maximum number is dictated by the maximum number of connections your DB will allow. For a moderate load this comes to about 100-300 connections when several applications are using the same database. For heavy loading this value can increase, but that depends on your definition of load.

The practical value is dictated by the max concurrent connections value of your data source. If this value is 100, a safe bet is to usually set it to N + 50% N where N is the maximum number of concurrent connections. Once again this is a generic thumb rule and should be aligned to the growth of connections in your application.


SCJP 6 articles - SCJP 5/6 mock exams - More SCJP Mocks
Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234

Thank you Deepak .
Andreas Barrud
Greenhorn

Joined: Jun 11, 2009
Posts: 12
In our produktion environment the typical number of connections is set to 10.
This is sufficient for us because the highest number of parallel connections is about 6 at a time.
If you have a lot of long lastig queryies that eat up your free connections then you might have a problem and get a lot of waiting connections and your performance will suffer or program faults due to timeouts.

Try to figure out how many parallel connections you have in your environment before setting the value to high (100 seems way to high for me!).
The company I am working for has about 3500 Users working with our WLS.
Ravi Kiran Va
Ranch Hand

Joined: Apr 18, 2009
Posts: 2234

Great answer .Thank You .
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6661
    
    5

100 seems way to high for me!


We once had a datasource that was accessed by about 15+ applications. Each application had an average maximum concurrent connections of 8. Under such cases the number of connections to be served is pretty high. It depends on overall load and 100 was used as an example.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Maximum Number of connections in Connection Pool.