First of all, thank you this detailed analysis of the situation.
Based on the bug report I suspected the driver, but it now seems clear
it was (at least part of) the problem.
re: Why was it necessary for the abandoned connection thread to act?
I'm not sure.. I looked into the JDBC Session manager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Colin,
On 3/19/13 2:29 PM, Colin Ingarfield wrote:
First of all, thank you this detailed analysis of the situation.
Based on the bug report I suspected the driver, but it now seems
clear it was (at least part of) the problem.
re: Why was it
On Tue, Mar 12, 2013 at 5:51 PM, Mark Thomas ma...@apache.org wrote:
On 12/03/2013 21:47, Colin Ingarfield wrote:
Hello,
We're using Jetty 8.1.3.v20120416 w/ JDBCSessionManager as our
application
server with Tomcat 7's JDBC Connection pool 7.0.28. We've run this
particular
On 15/03/2013 21:36, Colin Ingarfield wrote:
Short version:
Your upgrade to the latest Connector/J will have fixed this particular
problem.
Long version:
snip/
Found one Java-level deadlock: =
snip
Thread 1:
Here are the stack traces: Thread 12820: (state =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Colin,
On 3/14/13 3:41 PM, Colin Ingarfield wrote:
(Sorry I cannot reply correctly b/c I was on the digest list)
The deadlocked threads: Deadlock Detection:
Found one Java-level deadlock: =
qtp1840392480-3740:
On Fri, Mar 15, 2013 at 2:21 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Colin,
On 3/14/13 3:41 PM, Colin Ingarfield wrote:
(Sorry I cannot reply correctly b/c I was on the digest list)
The deadlocked threads: Deadlock
On 12/03/2013 21:47, Colin Ingarfield wrote:
Hello,
We're using Jetty 8.1.3.v20120416 w/ JDBCSessionManager as our application
server with Tomcat 7's JDBC Connection pool 7.0.28. We've run this
particular combination in production since at least Sept 2012. (Java 6 64
bit/Ubuntu, Amazon
