tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46201] jdbc-pool : con.close() should no-op if already closed
Date Thu, 13 Nov 2008 18:09:19 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46201


Filip Hanik <fhanik@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #1 from Filip Hanik <fhanik@apache.org>  2008-11-13 10:09:18 PST ---
By default, the connection pool is stateless, it doesn't keep track of any
connection state. This is for performance purposes to avoid roundtrips to the
DB.

There is an interceptor, called ConnectionState,
http://svn.apache.org/viewvc/tomcat/trunk/modules/jdbc-pool/java/org/apache/tomcat/jdbc/pool/interceptor/ConnectionState.java?view=log

that can keep track of state, and this one is also optimized to save roundtrips
to the database. so if autocommit hasn't changed, 

To configure the interceptor, one can look at 
http://svn.apache.org/viewvc/tomcat/trunk/modules/jdbc-pool/test/org/apache/tomcat/jdbc/test/TestConnectionState.java?view=log
for an example on how to use the connection state

this bug was fixed in 
http://svn.apache.org/viewvc?view=rev&revision=713763


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message