There is a one-to-one relationship between connections and transactions in your container. Not knowing your architecture, whether each of your request will spawn one txn, multiple serial txns, or multiple nested txns, I think the best rule-of-thumb is to set the max number of txns to be at least one greater than the number of execute threads in your container; this will minimize connection-starvation. Gene "Campano, Troy" wrote:I'm new to connection pooling. Could someone please tell me if I am on the right track?
If I set the amount of MAXIMUM ACTIVE CONNECTIONS to 4, does that mean that only 4 people can be logged into the web app or that there are 4 connections that are shared among all the users? Does this mean I want to set MAXIMUM ACTIVE CONNECTIONS to the amount of users I think would be using a webapp at a given time? Are there docs on how a lot of this connection pooling stuff works? I am using Tomcat with DBCP. thank you! ==========================================================================To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
