Connection refers to the connection to the DB but a user or something else in your app. The 4 connections you have are shared between your users, if they're available. Meaning when you getConnection() you're requesting a connection from the pooler. If you're only allowing 4 connections in use at any one time, and the pooler needs yet another connection to the DB, it will wait until one of the connections it returned, con.close(), then hand a connection to your request and get going. (At least this is how I understand it :-) ) > > > 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? No, load test your application to find out how many connections your application will need to have open with x number of users. A better way to do this I think is to set the MAX to what ever your DB will allow, then set the MIN to say 2 to ensure that when the load is not heavy you have at least 2 connections open and ready to service your requests. if you let it close all your connections completely, the first user to hit the app after a period of calm on your app will have to wait until the connection is open to the DB, then handed to your process.
> Are there docs on how a lot of this connection pooling stuff works? http://webdevelopersjournal.com/columns/connection_pool.html Robert S. Sfeir Senior Java Engineer gov.nih.cit.deca [EMAIL PROTECTED] "And eye for an eye results in the whole world going blind." -- Mohandas Ghandhi =========================================================================== 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
