Yes, from my understanding and use of other connection pool implementations, that is the way it is supposed to work.
Perhaps you are experiencing similar symptoms as myself. I have using the DBCP connection pool with MS SQL and have found that connections are being opened when there are already open connections that have been returned to the connection pool. I have checked all my code to ensure that a close() call exists and is in a finally block. When I switched to a different pooling implementation the problem disappeared. Is this the reason for your question? -----Original Message----- From: Rodney Waldhoff [mailto:[EMAIL PROTECTED]] Sent: December 9, 2002 6:00 PM To: Jakarta Commons Users List Subject: Re: DBCP not opening multiple connections Since DBCP pools connections, you should expect to see roughly no more connections created than are used in parallel, yes? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
