You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2006/07/31 06:46:14 UTC
[jira] Resolved: (DBCP-41) [dbcp][patch] docs lie: NOT maxIdle = 0
for no limit BUT -1
[ http://issues.apache.org/jira/browse/DBCP-41?page=all ]
Phil Steitz resolved DBCP-41.
-----------------------------
Resolution: Fixed
Patch applied. Thanks.
> [dbcp][patch] docs lie: NOT maxIdle = 0 for no limit BUT -1
> -----------------------------------------------------------
>
> Key: DBCP-41
> URL: http://issues.apache.org/jira/browse/DBCP-41
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.1
> Environment: Operating System: other
> Platform: Other
> Reporter: Anton Tagunov
> Fix For: 1.2.2
>
> Attachments: maxIdleNegativeForNoLimit.diff, maxIdleNegativeForNoLimitFixed.diff
>
>
> Documnentation for BasicDataSource and in a number of other places say: setMaxIdle( 0 ) for no limit. But GenericObjectPool says that _negative_ (-1 for instance) should be used for this purpose.
> In our neighbour project developers tried 0 and pool appeared to be non-functional: a new connection was created each time. They said: oh, well, drop dbcp, it does not work!
> I consider this doc update so critical that I'm submitting a patch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org