I copied the dev group too since it involved technical details (thread dumps, source code etc). Sorry if that sounds incorrect.
The traces I added are not incomplete. They are the ones we generated through the jmx api - ManagementFactory.getThreadMXBean().dumpAllThreads(true, true); On Thu, Mar 28, 2013 at 6:21 PM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: amit shah [mailto:amits...@gmail.com] > > To: Tomcat Users List; d...@tomcat.apache.org > > Do not cross-post. This belongs only on the users list. Read (and > follow) the mailing list usage rules. > > > Subject: Tomcat JDBC Connection Pool - Deadlock > > > The two threads involved in the deadlock have the below traces > > (from a thread dump) > > You'll need to show the complete traces for both threads, not just the > tail ends. > > - 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 > >
