Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of Chuck.Caldarale@unisys.com
 designates 216.82.243.203 as permitted sender)
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Wed, 8 May 2013 10:25:43 -0500
Subject: RE: Tomcat thread dump analysis
Thread-Topic: Tomcat thread dump analysis
Thread-Index: Ac5L+8lBQ/F37UPuRRCz6FSBFLUixQAAvHWg
Message-ID: 
 <99C8B2929B39C24493377AC7A121E21FC4AD16A25D@USEA-EXCH8.na.uis.unisys.com>
References: 
 <CAEzr04S1H_m47ygd2hB7Db+24kPD=67GepK3kQripTwD6kKUTw@mail.gmail.com>
	<3840CB1C-14C2-43C6-8A36-25587B5C4D10@gopivotal.com>
	<CAEzr04SEW0VLf5eWRXmUEZzqxynJ-JPQsQFXFS4Tnk18NOtKbA@mail.gmail.com>
	<518A484E.6050104@christopherschultz.net>
 <CAEzr04TBSWOTgaQNChdF3_YLsou40uwJbWLXO9jg3HiE=Tp_Sg@mail.gmail.com>
In-Reply-To: 
 <CAEzr04TBSWOTgaQNChdF3_YLsou40uwJbWLXO9jg3HiE=Tp_Sg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

> From: Charles Richard [mailto:charles.r@thelearningbar.com]=20
> Subject: Re: Tomcat thread dump analysis

> Top-posting is a post after another one I'm assuming?

No, it's doing what you keep on doing - posting the response before the que=
ry it applies to (you could have looked it up).  It's obnoxious and makes i=
t harder for people to follow the conversation.

> Here is a full thread dump

Which again shows no Tomcat involvement in the locking hang.  It would appe=
ar that logic in your application threads has either created a deadlock, or=
 failed to unlock something before returning, or something else entirely (e=
.g, broken network causing grief with Terracotta's distributed caching).  I=
f it's a deadlock, you need to examine the entire thread dump (all threads)=
 and look for a call stack that isn't like the others but holds the lock ev=
eryone else is waiting for.  If it's simply a failure to unlock somewhere, =
you will likely have to do a thorough code review to find it.  You will mos=
t likely need Terracotta's help here, since it's their code waiting on the =
lock.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL 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 atta=
chments from all computers.


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