[
https://issues.apache.org/jira/browse/OJB-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Armin Waibel closed OJB-124.
----------------------------
Resolution: Cannot Reproduce
Fix Version/s: 1.0.5
Hi Eric,
I agree with the other comments, this isn't a bug in OJB or DBCP. It seems the
connection pool was exhausted (and OJB doesn't automatically increase the pool
with the default settings). Maybe there are too many concurrent user or your
app cause a connection leak.
regards,
Armin
> 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: https://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
> Fix For: 1.0.5
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
