[
http://issues.apache.org/jira/browse/DBCP-196?page=comments#action_12442199 ]
Eric Ferrer commented on DBCP-196:
----------------------------------
[[ Old comment, sent by email on Wed, 9 Aug 2006 16:53:19 -0700 ]]
Hope this makes it on JIRA, didnt see a way to post a comment.
OJB is told to use DBCP for connection pooling and the following properties are
passed to it.
<jdbc-connection-descriptor jcd-alias="APPLICATION"
default-connection="true" platform="MsSQLServer" jdbc-level="4.0"
driver="net.sourceforge.jtds.jdbc.Driver"
dbalias="//myDatabase:4455/hDB;SelectMethod=cursor"
username="hDB" password="hDB"
eager-release="false" batch-mode="false" protocol="jdbc"
subprotocol="jtds:sqlserver"
useAutoCommit="1" ignoreAutoCommitExceptions="false">
<connection-pool maxActive="255" validationQuery="SELECT 1" />
</jdbc-connection-descriptor>
We have an enterprise license for SQL Server. Waiting to get information from
DBA on max number of concurrent users, etc.
---- "Henri Yandell (JIRA)" <[EMAIL PROTECTED]> wrote:
> 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: DBCP-196
> URL: http://issues.apache.org/jira/browse/DBCP-196
> Project: Commons Dbcp
> 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]
