> From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric B. > Subject: dbcp pool evictor deadlock? > > THREAD 1: > Name: Timer-1 > State: BLOCKED on > org.apache.tomcat.dbcp.dbcp.poolableconnect...@1e667871 > owned by: scheduling.QuartzInternal_Worker-0 > Total blocked: 1 Total waited: 15,342 > > Stack trace: > org.apache.tomcat.dbcp.dbcp.AbandonedTrace.addTrace(AbandonedTrace.java:175)
Assuming this version of Tomcat is using commons-dbcp 1.2.2, there's something seriously wrong here. The synchronized block at the above line is for an AbandonedTrace object, not a PoolableConnection. This is beginning to look like a broken JVM or broken hardware. Want to tell us what you're using for those (and the OS, while you're at it)? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
