commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DBCP-41) [dbcp][patch] docs lie: NOT maxIdle = 0 for no limit BUT -1
Date Sat, 08 Mar 2008 19:37:47 GMT

     [ https://issues.apache.org/jira/browse/DBCP-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz updated DBCP-41:
----------------------------

    Affects Version/s:     (was: 1.2.1)
                       1.2.2

maxActive documentation error applies to 1.2.2 configuration.xml.  Javadoc for BasicDataSource
also needs to be 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.


Mime
View raw message