File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes Connection Pool - No of connections Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Connection Pool - No of connections" Watch "Connection Pool - No of connections" New topic
Author

Connection Pool - No of connections

Malli Raman
Ranch Hand

Joined: Nov 07, 2001
Posts: 312
1. How to find out the maximum capacity of the Connection Pool for Weblogic Server 6.1 and Oracle 8i.
2. In my appln(Intranet), we expected that 500 user can access the database at a time. I don't know how to judge the max capacity (no of connections) of the connection Pool. Can i set it to 50 and set the autoshrink to True.
Regards,
Raman
--------------------
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
Set your capacity to some sufficiently high number, say 50 - 75. Make sure Oracle is configured to allow that many concurrent sessions (actually a few more), it shouldn't be a problem though because I think Oracle defaults to 200. Make sure Oracle will allow enough cursors to be open concurrently, especially if you are using the prepared statement cache.
Set on autoshrink.
Let it run that way for a few weeks and check the stats on the WebLogic and adjust accordingly based on those stats.
[ September 21, 2002: Message edited by: Chris Mathews ]
Dave Landers
Ranch Hand

Joined: Jul 24, 2002
Posts: 401
One thing to note - in normal circumstances, you can set your database connections to approximately the same as the number of execute threads. Uaually just a few more than that. The execute threads control how many user threads (i.e. call to servlet or RMI or EJB, etc) are running on the system at any one time, so you will not have more simultaneous database connections than that.
The exceptions are things like multiple connections per thread or stateful session beans that hang on to a connection and outlive the user thread, etc.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Connection Pool - No of connections