[ http://issues.apache.org/jira/browse/OJB-124?page=all ]
Phil Steitz moved DBCP-196 to OJB-124:
--------------------------------------
Project: OJB (was: Commons Dbcp)
Key: OJB-124 (was: DBCP-196)
> Unexpected error with DBCP and OJB where OJB was unable to get a connection.
> The root cause appears to be a org.apache.commons.dbcp.SQLNestedException:
> Cannot get a connection, pool exhausted, cause: null
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OJB-124
> URL: http://issues.apache.org/jira/browse/OJB-124
> Project: OJB
> Issue Type: Bug
> Environment: Jboss 4.0
> commons-dbcp-1.1.jar
> commons-pool-1.1.jar
> db-ojb-1.0.rc6.jar
> Reporter: Eric Ferrer
> Priority: Critical
> Attachments: dbcp_exhausted_connection_error.txt
>
>
> Our application has been running fine for 9 months and this is the first time
> I have encounted this error. It happend randomly throughout the day in an
> inconsistent pattern (user was entering data on web, user was searching for
> data, ect.) It did not occur on any particular screen. Attached is the
> stack trace from OJB Broker loadByExample request to DBCP error. THe rest of
> the stack trace was ommitted since it involves the uncaught exception entire
> stack back to the web tier
--
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]
