On Dec 11, 2010, at 1:18 AM, "Pid *" <p...@pidster.com> wrote:
> On 11 Dec 2010, at 01:07, Srikanth Konjarla <srikanth.konja...@gmail.com> > wrote: > >> BTW, I see some similarities with the following. >> >> https://jira.springframework.org/browse/SWS-533 > > Similarities in which sense? > The issue was closed as invalid. The similarity is that the thread is retained. However, other than the case is invalid it does not provide detail why it is invalid and why the thread is in WAIT state. If the thread is reused by tomcat, what happened to the references from previous cycle. I would be interested in learning. > > You're using Axis 1.4 which I've been looking at recently, because I > believe it causes a leak. I believe the same but wanted to make sure that leaking threads are captured and cleaned during the undeploy process. Additionally, I was wondering how I can detect and locate runaway Axis threads with thread locals. > > Please post the warnings from your logs so I can see of it's the same problem. Will do. Srikanth > > > p > >> >> Srikanth >> >> On 12/10/10 3:41 PM, Caldarale, Charles R wrote: >>>> From: Srikanth Konjarla [mailto:srikanth.konja...@gmail.com] >>>> Subject: Re: 6.0.26 java.lang.Thread.State: WAITING (on object monitor) >>> >>>> as part of the thread local cleanup process at the time of undeploy, >>>> tomcat removes few threadLocals but misses the threadLocals for the >>>> thread in question. I am wondering about the tomcat thread still being >>>> in "WAIT" mode and been cleaned up. >>> >>> The WAIT mode is normal - the thread is sitting in the pool, waiting for a >>> request to show up. I believe the ThreadLocal objects are discarded by >>> letting such infected threads exit and creating new ones. That's an area >>> still undergoing refinement, so you might want to try moving up to 6.0.29 >>> and see if it makes any difference. Or try sending in enough concurrent >>> requests to get all the threads busy and see if the references disappear >>> after that. >>> >>> - 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 >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
