Chuck, You are right. It is apache Axis client that is responsible for threadLocals in this case. However, 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.
Srikanth On 12/10/10 2:36 PM, Caldarale, Charles R wrote: >> From: Srikanth Konjarla [mailto:[email protected]] >> Subject: 6.0.26 java.lang.Thread.State: WAITING (on object monitor) > >> Essentially, the thread has threadLocals object that has >> few references. > > And who put the ThreadLocal there? (Hint: it wasn't Tomcat; your webapp - or > a library it's using - is behaving badly, and not cleaning up after itself.) > > - 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: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
