[ http://issues.apache.org/jira/browse/DBCP-41?page=all ]
Phil Steitz updated DBCP-41:
----------------------------
Bugzilla Id: (was: 35542)
Fix Version/s: 1.2.2
Affects Version/s: 1.2.1
(was: 1.2.2)
> [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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
