Hi,
OK, docs corrected and clarified. Thanks for pointing that out.
Yoav Shapira
Millennium Research Informatics
>-Original Message-
>From: Dirk Verbeeck [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, August 10, 2004 12:55 PM
>To: Tomcat Developers List
>Subject: Re: JDBC poo
This is a documentation bug, it should be:
A connection is considered idle when it is returned to the pool by
calling conn.close()
So by setting maxIdle=0 you never get any connection in the pool
effectively disabling the pooling.
This is probably not what you want.
In your case you want to us
