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 pool configuration bug
This is a documentation bug, it should be:
!-- Maximum number of idle dB connections to retain in pool.
Set to -1 for no limit.
--
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
hey,
i hope that i'm getting to the right people with this email. anyway,
the tomcat JDBC connection pool docs state:
!-- Maximum number of idle dB connections to retain in pool.
Set to 0 for no limit.
--
parameter
namemaxIdle/name
value30/value
/parameter
