As per the Wiki at http://wiki.apache.org/tomcat/FAQ/Miscellaneous#Q27
---
What order do webapps start (or how can I change startup order)?
There is no expected startup order. Neither the Servlet spec nor Tomcat
define one. You can't rely on the apps starting in any particular order.
---
Wonderi
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
>>
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 rem
adLocal has been forcibly removed.
On 12/13/10 4:23 AM, 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 Konj
On 12/12/10 8:28 AM, Pid * wrote:
> On 11 Dec 2010, at 21:39, Srikanth Konjarla
> wrote:
>
>>
>> On Dec 11, 2010, at 1:04 PM, "Pid *" wrote:
>>
>>> On 11 Dec 2010, at 20:02, Srikanth Konjarla
>>> wrote:
>>>
>>>> P
On Dec 11, 2010, at 1:04 PM, "Pid *" wrote:
> On 11 Dec 2010, at 20:02, Srikanth Konjarla
> wrote:
>
>> Pid,
>>
>> Thanks for your patience. Here is the output from catalina.out file
>> while the webapp is being undeployed. As you can see there
vent a memory
leak, the ThreadLocal has been forcibly removed.
Srikanth
On 12/11/10 2:26 AM, Pid wrote:
> On 12/11/10 9:25 AM, Srikanth Konjarla wrote:
>>
>>
>> On Dec 11, 2010, at 1:18 AM, "Pid *&qu
On Dec 11, 2010, at 1:18 AM, "Pid *" wrote:
> On 11 Dec 2010, at 01:07, Srikanth Konjarla
> wrote:
>
>> BTW, I see some similarities with the following.
>>
>> https://jira.springframework.org/browse/SWS-533
>
> Similarities in which sense?
> T
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 ob
On 12/10/10 4:11 PM, Pid * wrote:
> On 10 Dec 2010, at 22:46, Srikanth Konjarla
> wrote:
>
>> 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
>>
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,
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)
>
>> Essential
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 java.lang.Object.wai
13 matches
Mail list logo
