This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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 --------------------
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 ]
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’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com