xplanner

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 0.7
• Fix Version/s: 0.7
• Component/s: Overall
• Labels:

  None

If you open a session, wait for some time (30-40 minutes) and then click on a link, the link works but in the Tomcat-logs appears something like this:

2005-10-30 08:48:35,325 [Timer-0] WARN async.ThreadPoolAsynchronousRunner - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@67da00 -- APPARENT DEA
DLOCK!!! Creating emergency threads for unassigned pending tasks!
2005-10-30 08:48:35,325 [Timer-0] WARN async.ThreadPoolAsynchronousRunner - com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@67da00 -- APPARENT DEA
DLOCK!!! Complete Status: [num_managed_threads: 3, num_active: 3; activeTasks: com.mchange.v2.resourcepool.BasicResourcePool$5@44239d (com.mchange.v2.async.ThreadPool
AsynchronousRunner$PoolThread-#1), com.mchange.v2.resourcepool.BasicResourcePool$5@17e1a9b (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0), com.mcha
nge.v2.resourcepool.BasicResourcePool$5@4c123 (com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2); pendingTasks: com.mchange.v2.resourcepool.BasicResour
cePool$AcquireTask@23e5f8, com.mchange.v2.resourcepool.BasicResourcePool$5@cf1ca7, com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1622bd8, com.mchange.v2.r
esourcepool.BasicResourcePool$5@2ca6ee, com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@183838f, com.mchange.v2.resourcepool.BasicResourcePool$5@13244f0, co
m.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@14c07f3, com.mchange.v2.resourcepool.BasicResourcePool$5@9dfac7, com.mchange.v2.resourcepool.BasicResourcePool
$AcquireTask@1bb33a6, com.mchange.v2.resourcepool.BasicResourcePool$5@13be583, com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1590b7a, com.mchange.v2.c3p0.
stmt.GooGooStatementCache$2@1008189, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@384dfd, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@881d27, com.mchange.v2.c3
p0.stmt.GooGooStatementCache$2@322528, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@25a2be, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@df7a7c, com.mchange.v2.
c3p0.stmt.GooGooStatementCache$2@1e274c6, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@60b3bb, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@b7c991, com.mchange.
v2.c3p0.stmt.GooGooStatementCache$2@127f2b, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@5b1b95, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@17009c0, com.mchan
ge.v2.c3p0.stmt.GooGooStatementCache$2@901e03, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@1a26fdd, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@15e39e2, com.m
change.v2.c3p0.stmt.GooGooStatementCache$3@12a3aac, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@1720e7f, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@115cf42,
com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@da20ab, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@96d9c3, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@1b29bc
4, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@1107f7a, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@214916, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@14
557ef, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@1901cf9, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@5e483d, com.mchange.v2.c3p0.stmt.GooGooStatementCache$
2@1d8dd9b, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@bd1c46, com.mchange.v2.c3p0.stmt.GooGooStatementCache$2@18b4353, com.mchange.v2.c3p0.stmt.GooGooStatementCa
che$2@1f12c12]

Tomcat becomes unresponsible after this and has to be restarted which has a severe impact on all other applications running on the same server.

Issue XPR-151 seems to be caused by this, too.

This issue duplicates:
XPR-151	charts for Iteration Progress and Iteration Burn Down are empty

• Assignee:

  Mateusz Prokopowicz

  Reporter:

  Kurt Huwig

• Created:

  30/Oct/05 2:01 AM

  Updated:

  30/Nov/05 2:25 AM

  Resolved:

  11/Nov/05 10:52 PM