On 15/12/2010 15:37, Srikanth Konjarla wrote:
On 12/15/10 7:13 AM, Pid wrote:
On 15/12/2010 02:40, Srikanth Konjarla wrote:
I could catch Axis threadlocals from the app to clean up. However, I
have a question wrt following tomcat's log at the time of undeploy of
app. The message suggests
On 12/17/10 3:01 AM, Pid wrote:
On 15/12/2010 15:37, Srikanth Konjarla wrote:
On 12/15/10 7:13 AM, Pid wrote:
On 15/12/2010 02:40, Srikanth Konjarla wrote:
I could catch Axis threadlocals from the app to clean up. However, I
have a question wrt following tomcat's log at the time of
On 17/12/2010 15:38, Srikanth Konjarla wrote:
On 12/17/10 3:01 AM, Pid wrote:
On 15/12/2010 15:37, Srikanth Konjarla wrote:
On 12/15/10 7:13 AM, Pid wrote:
On 15/12/2010 02:40, Srikanth Konjarla wrote:
I could catch Axis threadlocals from the app to clean up. However, I
have a question
On 15/12/2010 02:40, Srikanth Konjarla wrote:
I could catch Axis threadlocals from the app to clean up. However, I
have a question wrt following tomcat's log at the time of undeploy of
app. The message suggests that it is removing the same threadlocal
twice. Is it because it was not removed in
On 12/15/10 7:13 AM, Pid wrote:
On 15/12/2010 02:40, Srikanth Konjarla wrote:
I could catch Axis threadlocals from the app to clean up. However, I
have a question wrt following tomcat's log at the time of undeploy of
app. The message suggests that it is removing the same threadlocal
twice.
: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
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
On 13/12/2010 12:23, Pid wrote:
On 12/12/2010 18:18, Srikanth Konjarla wrote:
On 12/12/10 8:28 AM, Pid * wrote:
On 11 Dec 2010, at 21:39, Srikanth Konjarla srikanth.konja...@gmail.com
wrote:
On Dec 11, 2010, at 1:04 PM, Pid * p...@pidster.com wrote:
On 11 Dec 2010, at 20:02, Srikanth
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
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
: 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
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
: 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
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
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
Some short answers :
- (for the moment) threads are always reused, even after an application is
stopped.
- tomcat 6.0.26 tries to clean the threadlocals which may provoke a leak, but
1) it was unsafe and has been disabled by default from 6.0.27 (see
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
All,
I have a webservice client in the webapp. When the webapp is undeployed
the classloader has not been GC'ed. Upon investigation it is found that
a thread is in WAIT state which has references to the webapp class
loader. I see the following from heap dump.
http-8080-2
at
From: Srikanth Konjarla [mailto:srikanth.konja...@gmail.com]
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
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:srikanth.konja...@gmail.com]
Subject: 6.0.26 java.lang.Thread.State: WAITING (on object monitor)
Essentially, the thread has threadLocals object
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
using here.
p
Srikanth
On 12/10/10 2:36 PM, Caldarale, Charles R wrote:
From: Srikanth Konjarla [mailto:srikanth.konja...@gmail.com]
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
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
...@gmail.com]
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
BTW, I see some similarities with the following.
https://jira.springframework.org/browse/SWS-533
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
25 matches
Mail list logo
