commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Logemann <>
Subject DBCP: returning non-existant connections
Date Tue, 16 Jul 2002 10:04:27 GMT

i am getting back connections that physically doesnt exists from
DBCP. This happens from time to time and i cant see a pattern. Sometimes
(when doing a reload on a servlet) its happens every second time.

in this trace you see 3 connections that were established without problems. After
the "ok", i ve done another request, but this time, the @18c connection
is physically not there. On my database machine, i see only one connection
(i cant see which object of the three holds the one physical connection), but
obviously its not the @18c

Despite the connections on my DB machine are varying quite often. I allways thought
that i have something like a constant number of open connections to my database which will
be reused.

Any thoughts are welcome, also any thoughts on how to trace this better...

Starting service Tomcat-Standalone
Apache Tomcat/4.0.4
Using Connection: org.apache.commons.dbcp.PoolableConnection@e7c5cb
Using Connection: org.apache.commons.dbcp.PoolableConnection@18c74
Using Connection: org.apache.commons.dbcp.PoolableConnection@21e554
Using Connection: org.apache.commons.dbcp.PoolableConnection@18c74
java.sql.SQLException: The connection does not exist.
        at Source)
        at Source)
        at Source)
        at Sour
        at Sour
        at org.apache.commons.dbcp.DelegatingConnection.createStatement(Delegati
        at de.bahr.businessobjects.GateKeeper.authentify(
greetings from
Marc Logemann
Homebase @

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message