I'm guessing somewhere in your code, you're calling close() on a
connection and that's bringing up this exception.
It would appear org.apache.commons.dbcp.PoolableConnection is going
against the Sun javadocs for at least java 5 which states that calling
close() on an already closed connection is a no-op. Doesn't look like
an exception should be thrown here.
Probably your best bet is to ask the DBCP folks since tomcat uses there
code directly with only a refactoring of the package name.
--David
Eickvonder Bjoern wrote:
Hi,
I just discovered a minor difference in the DHCP implementation used in
Tomcat 5.5.25 vs. 5.5.23 and I'd like to know if it is a bug or a
feature.
I use conncetion pooling with minIdle>0 (but no validationQuery), so a
few connection will remain open all day long. If the database now closes
the connection itself (either due to timeout or server restart), this
was no problem in Tomcat 5.5.23. The DHCP implementation kicked out the
already closed connection out of the pool and established a new one that
is returned.
Now in Tomcat 5.5.25 the connection seems to be kicked out as well in
the end but an exception is propageted to the caller.
Caused by: java.sql.SQLException: Already closed.
at
org.apache.tomcat.dbcp.dbcp.PoolableConnection.close(PoolableConnection.
java:84)
at
org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper
.close(PoolingDataSource.java:181)
at
org.jpox.store.rdbms.adapter.DatabaseAdapter.getConnection(DatabaseAdapt
er.java:928)
at
org.jpox.store.rdbms.RDBMSNonmanagedTransaction.begin(RDBMSNonmanagedTra
nsaction.java:324)
... 57 more
Is this a bug?
Bjoern Eickvonder
Kennen Sie schon die inside Schulungsma?nahme zur VVG-Reform? Erfahren Sie mehr dazu unter www.vvg-konzept.de.
Besuchen Sie uns an unserem Stand C 8 auf der Learntec in Karlsruhe vom
29.-31.01.08.
Diese Mitteilung ist vertraulich und ausschlie?lich an den entsprechenden
Empfanger gerichtet. Wenn Sie diese Mitteilung versehentlich erhalten haben,
durfen Sie diese nicht kopieren, weitergeben oder in sonstiger Weise
verbreiten. Bitte informieren Sie in einem solchen Fall den Absender und
loschen Sie die Mitteilung sowie alle zugehorigen Anhange.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
