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 2007/07/22 01:48:06 UTC
[jira] Resolved: (DBCP-232) maxWait = 0 waits indefinitely too,
not only maxWait = -1
[ https://issues.apache.org/jira/browse/DBCP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz resolved DBCP-232.
------------------------------
Resolution: Fixed
Javadoc fix committed in r558394. Thanks for reporting thi
> maxWait = 0 waits indefinitely too, not only maxWait = -1
> ----------------------------------------------------------
>
> Key: DBCP-232
> URL: https://issues.apache.org/jira/browse/DBCP-232
> Project: Commons Dbcp
> Issue Type: Improvement
> Environment: all
> Reporter: Peter Welkenbach
> Priority: Critical
>
> the documentation describes the maxWait property as:
> "The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception, or -1 to wait indefinitely."
> this seems to be wrong. Compared to the source code it should be
> "for a connection to be returned before throwing an exception, or -1 or 0 to wait indefinitely."
> in the source code of class GenericObjectPool the comparison is "maxWait <= 0"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org