[
https://issues.apache.org/jira/browse/DBCP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-41.
-----------------------------
Resolution: Fixed
> [dbcp][patch] docs lie: NOT maxIdle = 0 for no limit BUT -1
> -----------------------------------------------------------
>
> Key: DBCP-41
> URL: https://issues.apache.org/jira/browse/DBCP-41
> Project: Commons Dbcp
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Operating System: other
> Platform: Other
> Reporter: Anton Tagunov
> Fix For: 1.3
>
> 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.
-
You can reply to this email to add a comment to the issue online.
