[jira] Commented: (OJB-124) 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

    [ http://issues.apache.org/jira/browse/OJB-124?page=comments#action_12452513 ] 
            
Phil Steitz commented on OJB-124:
---------------------------------

From the stacktrace, it looks to me as though the pool is periodically becoming exhausted and the pool is configured to fail (i.e, throw the NoSuchElementException in the trace) when exhausted.  I am unfortunately not familiar with OJB, but the config fragment above does not appear to set the whenExhaustedAction property of the pool.  The default config for the pool sets this to WHEN_EXHAUSTED_BLOCK,  but it looks like OJB defaults this to WHEN_EXHAUSTED_FAIL (see org.apache.ojb.broker.util.pooling.PoolConfiguration).  I suggest modifying the OJB config appropriately to increase the pool size or change the whenExhaustedAction.

I don't think this is a dbcp or pool bug.  Moving to ojb.

> 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