You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Chinmoy Chakraborty <cc...@gmail.com> on 2010/03/08 16:25:10 UTC
Possible memory leak in Axis2 1.4.1?
Hi All,
I have an application which uses Axis2 1.4.1. When we have Axis2 configured
(servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
"*A web application appears to have started a thread named [Timer-0] but has
failed to stop it. This is very likely to create a memory leak*".
According to tomcat developers this happens when an app starts a thread but
never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
fails to stop the thread, it gives above message.
If we comment out Axis2 servlet mappings in web.xml we do not get the error.
Any comments?
Chinmoy
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Please ignore my previous mail...the error occurs with jdk 1.5 also....I
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 with the same version of
> tomcat. In the previous report we saw there were two classes under DEFUNCT
> head and both the classes extends TimerTask.
>
> Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Andreas,
>>
>> Following is the report I got after stopping our app:
>>
>> /arit-war-0.1
>>
>> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>
>> <defunct>
>>
>> - Timer thread; tasks:
>> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> - Timer thread; tasks: labware.util.ResourceMonitor
>>
>> labware.util.ResourceMonitor is our class but once I comment out axis2
>> entries in web.xml I do not get the error.
>>
>> Chinmoy
>>
>>
>>
>> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Chinmoy,
>>>
>>> The important test is actually to get the arit report after stopping
>>> the Axis2 application. This will really show the leaked resources
>>> (under "<defunct>"). Can you do this and post the result?
>>>
>>> Andreas
>>>
>>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>>> wrote:
>>> > Amila,
>>> > Still I get the error after switching off following parameter:
>>> >
>>> > <parameter name="hotdeployment">false</parameter>
>>> > <parameter name="hotupdate">false</parameter>
>>> > Andreas,
>>> > I get following report when I tried
>>> http://localhost:8080/arit-war-0.1/ :
>>> > /arit-war-0.1
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209 (this is our app)
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > I commented out SOAPMonitorService from web.xml but still I get the
>>> error.
>>> > It seems that the problem lies in
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>>> At
>>> > this point both the above mentioned parameters are switched off.
>>> > Now if I switched on those params I get following report from arit:
>>> >
>>> > /arit-war-0.1
>>> >
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209
>>> >
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > Chinmoy
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>>> > <am...@gmail.com> wrote:
>>> >>
>>> >>
>>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cchinu@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>> Hi All,
>>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> >>> configured (servlet mappings) in web.xml we get following error in
>>> Tomcat
>>> >>> 6.0.24.
>>> >>> "A web application appears to have started a thread named [Timer-0]
>>> but
>>> >>> has failed to stop it. This is very likely to create a memory leak".
>>> >>
>>> >> Axis2 starts a new timer task to pool the deployment directory. This
>>> >> could be this thread.
>>> >> try switch offing hotUpdate
>>> >> <parameter name="hotdeployment">false</parameter>
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>>
>>> >>> According to tomcat developers this happens when an app starts a
>>> thread
>>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>>> if
>>> >>> tomcat fails to stop the thread, it gives above message.
>>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> >>> error.
>>> >>> Any comments?
>>> >>> Chinmoy
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Please ignore my previous mail...the error occurs with jdk 1.5 also....I
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 with the same version of
> tomcat. In the previous report we saw there were two classes under DEFUNCT
> head and both the classes extends TimerTask.
>
> Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Andreas,
>>
>> Following is the report I got after stopping our app:
>>
>> /arit-war-0.1
>>
>> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>
>> <defunct>
>>
>> - Timer thread; tasks:
>> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> - Timer thread; tasks: labware.util.ResourceMonitor
>>
>> labware.util.ResourceMonitor is our class but once I comment out axis2
>> entries in web.xml I do not get the error.
>>
>> Chinmoy
>>
>>
>>
>> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Chinmoy,
>>>
>>> The important test is actually to get the arit report after stopping
>>> the Axis2 application. This will really show the leaked resources
>>> (under "<defunct>"). Can you do this and post the result?
>>>
>>> Andreas
>>>
>>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>>> wrote:
>>> > Amila,
>>> > Still I get the error after switching off following parameter:
>>> >
>>> > <parameter name="hotdeployment">false</parameter>
>>> > <parameter name="hotupdate">false</parameter>
>>> > Andreas,
>>> > I get following report when I tried
>>> http://localhost:8080/arit-war-0.1/ :
>>> > /arit-war-0.1
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209 (this is our app)
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > I commented out SOAPMonitorService from web.xml but still I get the
>>> error.
>>> > It seems that the problem lies in
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>>> At
>>> > this point both the above mentioned parameters are switched off.
>>> > Now if I switched on those params I get following report from arit:
>>> >
>>> > /arit-war-0.1
>>> >
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209
>>> >
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > Chinmoy
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>>> > <am...@gmail.com> wrote:
>>> >>
>>> >>
>>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cchinu@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>> Hi All,
>>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> >>> configured (servlet mappings) in web.xml we get following error in
>>> Tomcat
>>> >>> 6.0.24.
>>> >>> "A web application appears to have started a thread named [Timer-0]
>>> but
>>> >>> has failed to stop it. This is very likely to create a memory leak".
>>> >>
>>> >> Axis2 starts a new timer task to pool the deployment directory. This
>>> >> could be this thread.
>>> >> try switch offing hotUpdate
>>> >> <parameter name="hotdeployment">false</parameter>
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>>
>>> >>> According to tomcat developers this happens when an app starts a
>>> thread
>>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>>> if
>>> >>> tomcat fails to stop the thread, it gives above message.
>>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> >>> error.
>>> >>> Any comments?
>>> >>> Chinmoy
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Please ignore my previous mail...the error occurs with jdk 1.5 also....I
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 with the same version of
> tomcat. In the previous report we saw there were two classes under DEFUNCT
> head and both the classes extends TimerTask.
>
> Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Andreas,
>>
>> Following is the report I got after stopping our app:
>>
>> /arit-war-0.1
>>
>> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>
>> <defunct>
>>
>> - Timer thread; tasks:
>> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> - Timer thread; tasks: labware.util.ResourceMonitor
>>
>> labware.util.ResourceMonitor is our class but once I comment out axis2
>> entries in web.xml I do not get the error.
>>
>> Chinmoy
>>
>>
>>
>> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Chinmoy,
>>>
>>> The important test is actually to get the arit report after stopping
>>> the Axis2 application. This will really show the leaked resources
>>> (under "<defunct>"). Can you do this and post the result?
>>>
>>> Andreas
>>>
>>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>>> wrote:
>>> > Amila,
>>> > Still I get the error after switching off following parameter:
>>> >
>>> > <parameter name="hotdeployment">false</parameter>
>>> > <parameter name="hotupdate">false</parameter>
>>> > Andreas,
>>> > I get following report when I tried
>>> http://localhost:8080/arit-war-0.1/ :
>>> > /arit-war-0.1
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209 (this is our app)
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > I commented out SOAPMonitorService from web.xml but still I get the
>>> error.
>>> > It seems that the problem lies in
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>>> At
>>> > this point both the above mentioned parameters are switched off.
>>> > Now if I switched on those params I get following report from arit:
>>> >
>>> > /arit-war-0.1
>>> >
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209
>>> >
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > Chinmoy
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>>> > <am...@gmail.com> wrote:
>>> >>
>>> >>
>>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cchinu@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>> Hi All,
>>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> >>> configured (servlet mappings) in web.xml we get following error in
>>> Tomcat
>>> >>> 6.0.24.
>>> >>> "A web application appears to have started a thread named [Timer-0]
>>> but
>>> >>> has failed to stop it. This is very likely to create a memory leak".
>>> >>
>>> >> Axis2 starts a new timer task to pool the deployment directory. This
>>> >> could be this thread.
>>> >> try switch offing hotUpdate
>>> >> <parameter name="hotdeployment">false</parameter>
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>>
>>> >>> According to tomcat developers this happens when an app starts a
>>> thread
>>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>>> if
>>> >>> tomcat fails to stop the thread, it gives above message.
>>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> >>> error.
>>> >>> Any comments?
>>> >>> Chinmoy
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Please ignore my previous mail...the error occurs with jdk 1.5 also....I
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 with the same version of
> tomcat. In the previous report we saw there were two classes under DEFUNCT
> head and both the classes extends TimerTask.
>
> Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Andreas,
>>
>> Following is the report I got after stopping our app:
>>
>> /arit-war-0.1
>>
>> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>
>> <defunct>
>>
>> - Timer thread; tasks:
>> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> - Timer thread; tasks: labware.util.ResourceMonitor
>>
>> labware.util.ResourceMonitor is our class but once I comment out axis2
>> entries in web.xml I do not get the error.
>>
>> Chinmoy
>>
>>
>>
>> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Chinmoy,
>>>
>>> The important test is actually to get the arit report after stopping
>>> the Axis2 application. This will really show the leaked resources
>>> (under "<defunct>"). Can you do this and post the result?
>>>
>>> Andreas
>>>
>>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>>> wrote:
>>> > Amila,
>>> > Still I get the error after switching off following parameter:
>>> >
>>> > <parameter name="hotdeployment">false</parameter>
>>> > <parameter name="hotupdate">false</parameter>
>>> > Andreas,
>>> > I get following report when I tried
>>> http://localhost:8080/arit-war-0.1/ :
>>> > /arit-war-0.1
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209 (this is our app)
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > I commented out SOAPMonitorService from web.xml but still I get the
>>> error.
>>> > It seems that the problem lies in
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>>> At
>>> > this point both the above mentioned parameters are switched off.
>>> > Now if I switched on those params I get following report from arit:
>>> >
>>> > /arit-war-0.1
>>> >
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209
>>> >
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > Chinmoy
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>>> > <am...@gmail.com> wrote:
>>> >>
>>> >>
>>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cchinu@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>> Hi All,
>>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> >>> configured (servlet mappings) in web.xml we get following error in
>>> Tomcat
>>> >>> 6.0.24.
>>> >>> "A web application appears to have started a thread named [Timer-0]
>>> but
>>> >>> has failed to stop it. This is very likely to create a memory leak".
>>> >>
>>> >> Axis2 starts a new timer task to pool the deployment directory. This
>>> >> could be this thread.
>>> >> try switch offing hotUpdate
>>> >> <parameter name="hotdeployment">false</parameter>
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>>
>>> >>> According to tomcat developers this happens when an app starts a
>>> thread
>>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>>> if
>>> >>> tomcat fails to stop the thread, it gives above message.
>>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> >>> error.
>>> >>> Any comments?
>>> >>> Chinmoy
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Please ignore my previous mail...the error occurs with jdk 1.5 also....I
guess it's Axis2 issue...
On Tue, Mar 9, 2010 at 3:28 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6
> but I do not get this error if I use jdk 1.5 with the same version of
> tomcat. In the previous report we saw there were two classes under DEFUNCT
> head and both the classes extends TimerTask.
>
> Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Andreas,
>>
>> Following is the report I got after stopping our app:
>>
>> /arit-war-0.1
>>
>> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>
>> <defunct>
>>
>> - Timer thread; tasks:
>> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> - Timer thread; tasks: labware.util.ResourceMonitor
>>
>> labware.util.ResourceMonitor is our class but once I comment out axis2
>> entries in web.xml I do not get the error.
>>
>> Chinmoy
>>
>>
>>
>> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
>> andreas.veithen@gmail.com> wrote:
>>
>>> Chinmoy,
>>>
>>> The important test is actually to get the arit report after stopping
>>> the Axis2 application. This will really show the leaked resources
>>> (under "<defunct>"). Can you do this and post the result?
>>>
>>> Andreas
>>>
>>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>>> wrote:
>>> > Amila,
>>> > Still I get the error after switching off following parameter:
>>> >
>>> > <parameter name="hotdeployment">false</parameter>
>>> > <parameter name="hotupdate">false</parameter>
>>> > Andreas,
>>> > I get following report when I tried
>>> http://localhost:8080/arit-war-0.1/ :
>>> > /arit-war-0.1
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209 (this is our app)
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > I commented out SOAPMonitorService from web.xml but still I get the
>>> error.
>>> > It seems that the problem lies in
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>>> At
>>> > this point both the above mentioned parameters are switched off.
>>> > Now if I switched on those params I get following report from arit:
>>> >
>>> > /arit-war-0.1
>>> >
>>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>>> >
>>> > /web3_dev_1209
>>> >
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Timer thread; tasks:
>>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>>> > Thread,
>>> >
>>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>>> >
>>> > Chinmoy
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>>> > <am...@gmail.com> wrote:
>>> >>
>>> >>
>>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cchinu@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>> Hi All,
>>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> >>> configured (servlet mappings) in web.xml we get following error in
>>> Tomcat
>>> >>> 6.0.24.
>>> >>> "A web application appears to have started a thread named [Timer-0]
>>> but
>>> >>> has failed to stop it. This is very likely to create a memory leak".
>>> >>
>>> >> Axis2 starts a new timer task to pool the deployment directory. This
>>> >> could be this thread.
>>> >> try switch offing hotUpdate
>>> >> <parameter name="hotdeployment">false</parameter>
>>> >>
>>> >> thanks,
>>> >> Amila.
>>> >>>
>>> >>> According to tomcat developers this happens when an app starts a
>>> thread
>>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>>> if
>>> >>> tomcat fails to stop the thread, it gives above message.
>>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> >>> error.
>>> >>> Any comments?
>>> >>> Chinmoy
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Amila Suriarachchi
>>> >> WSO2 Inc.
>>> >> blog: http://amilachinthaka.blogspot.com/
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>
>>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
Chinmoy
On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> - Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> - Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
Chinmoy
On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> - Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> - Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was designed as a module.
Andreas
On Tue, Mar 9, 2010 at 13:35, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> After removing scripting module, the error is gone. Is this bug is fixed in
> Axis2 1.5.1? and what exactly we can do with scripting module?
> Thanks a lot.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> This could be related to AXIS2-4263. Can you try the workaround(s)
>> proposed in that issue?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Andreas,
>> > Following is the report I got after stopping our app:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > <defunct>
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks: labware.util.ResourceMonitor
>> >
>> > labware.util.ResourceMonitor is our class but once I comment out axis2
>> > entries in web.xml I do not get the error.
>> > Chinmoy
>> >
>> >
>> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Chinmoy,
>> >>
>> >> The important test is actually to get the arit report after stopping
>> >> the Axis2 application. This will really show the leaked resources
>> >> (under "<defunct>"). Can you do this and post the result?
>> >>
>> >> Andreas
>> >>
>> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >> > Amila,
>> >> > Still I get the error after switching off following parameter:
>> >> >
>> >> > <parameter name="hotdeployment">false</parameter>
>> >> > <parameter name="hotupdate">false</parameter>
>> >> > Andreas,
>> >> > I get following report when I
>> >> > tried http://localhost:8080/arit-war-0.1/
>> >> > :
>> >> > /arit-war-0.1
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209 (this is our app)
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > I commented out SOAPMonitorService from web.xml but still I get the
>> >> > error.
>> >> > It seems that the problem lies in
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>> >> > At
>> >> > this point both the above mentioned parameters are switched off.
>> >> > Now if I switched on those params I get following report from arit:
>> >> >
>> >> > /arit-war-0.1
>> >> >
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209
>> >> >
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > Chinmoy
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> >> > <am...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty
>> >> >> <cc...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi All,
>> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >> >>> configured (servlet mappings) in web.xml we get following error in
>> >> >>> Tomcat
>> >> >>> 6.0.24.
>> >> >>> "A web application appears to have started a thread named [Timer-0]
>> >> >>> but
>> >> >>> has failed to stop it. This is very likely to create a memory
>> >> >>> leak".
>> >> >>
>> >> >> Axis2 starts a new timer task to pool the deployment directory.
>> >> >> This
>> >> >> could be this thread.
>> >> >> try switch offing hotUpdate
>> >> >> <parameter name="hotdeployment">false</parameter>
>> >> >>
>> >> >> thanks,
>> >> >> Amila.
>> >> >>>
>> >> >>> According to tomcat developers this happens when an app starts a
>> >> >>> thread
>> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22
>> >> >>> onwards)
>> >> >>> if
>> >> >>> tomcat fails to stop the thread, it gives above message.
>> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
>> >> >>> the
>> >> >>> error.
>> >> >>> Any comments?
>> >> >>> Chinmoy
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Amila Suriarachchi
>> >> >> WSO2 Inc.
>> >> >> blog: http://amilachinthaka.blogspot.com/
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was designed as a module.
Andreas
On Tue, Mar 9, 2010 at 13:35, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> After removing scripting module, the error is gone. Is this bug is fixed in
> Axis2 1.5.1? and what exactly we can do with scripting module?
> Thanks a lot.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> This could be related to AXIS2-4263. Can you try the workaround(s)
>> proposed in that issue?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Andreas,
>> > Following is the report I got after stopping our app:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > <defunct>
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks: labware.util.ResourceMonitor
>> >
>> > labware.util.ResourceMonitor is our class but once I comment out axis2
>> > entries in web.xml I do not get the error.
>> > Chinmoy
>> >
>> >
>> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Chinmoy,
>> >>
>> >> The important test is actually to get the arit report after stopping
>> >> the Axis2 application. This will really show the leaked resources
>> >> (under "<defunct>"). Can you do this and post the result?
>> >>
>> >> Andreas
>> >>
>> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >> > Amila,
>> >> > Still I get the error after switching off following parameter:
>> >> >
>> >> > <parameter name="hotdeployment">false</parameter>
>> >> > <parameter name="hotupdate">false</parameter>
>> >> > Andreas,
>> >> > I get following report when I
>> >> > tried http://localhost:8080/arit-war-0.1/
>> >> > :
>> >> > /arit-war-0.1
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209 (this is our app)
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > I commented out SOAPMonitorService from web.xml but still I get the
>> >> > error.
>> >> > It seems that the problem lies in
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>> >> > At
>> >> > this point both the above mentioned parameters are switched off.
>> >> > Now if I switched on those params I get following report from arit:
>> >> >
>> >> > /arit-war-0.1
>> >> >
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209
>> >> >
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > Chinmoy
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> >> > <am...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty
>> >> >> <cc...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi All,
>> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >> >>> configured (servlet mappings) in web.xml we get following error in
>> >> >>> Tomcat
>> >> >>> 6.0.24.
>> >> >>> "A web application appears to have started a thread named [Timer-0]
>> >> >>> but
>> >> >>> has failed to stop it. This is very likely to create a memory
>> >> >>> leak".
>> >> >>
>> >> >> Axis2 starts a new timer task to pool the deployment directory.
>> >> >> This
>> >> >> could be this thread.
>> >> >> try switch offing hotUpdate
>> >> >> <parameter name="hotdeployment">false</parameter>
>> >> >>
>> >> >> thanks,
>> >> >> Amila.
>> >> >>>
>> >> >>> According to tomcat developers this happens when an app starts a
>> >> >>> thread
>> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22
>> >> >>> onwards)
>> >> >>> if
>> >> >>> tomcat fails to stop the thread, it gives above message.
>> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
>> >> >>> the
>> >> >>> error.
>> >> >>> Any comments?
>> >> >>> Chinmoy
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Amila Suriarachchi
>> >> >> WSO2 Inc.
>> >> >> blog: http://amilachinthaka.blogspot.com/
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was designed as a module.
Andreas
On Tue, Mar 9, 2010 at 13:35, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> After removing scripting module, the error is gone. Is this bug is fixed in
> Axis2 1.5.1? and what exactly we can do with scripting module?
> Thanks a lot.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> This could be related to AXIS2-4263. Can you try the workaround(s)
>> proposed in that issue?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Andreas,
>> > Following is the report I got after stopping our app:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > <defunct>
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks: labware.util.ResourceMonitor
>> >
>> > labware.util.ResourceMonitor is our class but once I comment out axis2
>> > entries in web.xml I do not get the error.
>> > Chinmoy
>> >
>> >
>> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Chinmoy,
>> >>
>> >> The important test is actually to get the arit report after stopping
>> >> the Axis2 application. This will really show the leaked resources
>> >> (under "<defunct>"). Can you do this and post the result?
>> >>
>> >> Andreas
>> >>
>> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >> > Amila,
>> >> > Still I get the error after switching off following parameter:
>> >> >
>> >> > <parameter name="hotdeployment">false</parameter>
>> >> > <parameter name="hotupdate">false</parameter>
>> >> > Andreas,
>> >> > I get following report when I
>> >> > tried http://localhost:8080/arit-war-0.1/
>> >> > :
>> >> > /arit-war-0.1
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209 (this is our app)
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > I commented out SOAPMonitorService from web.xml but still I get the
>> >> > error.
>> >> > It seems that the problem lies in
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>> >> > At
>> >> > this point both the above mentioned parameters are switched off.
>> >> > Now if I switched on those params I get following report from arit:
>> >> >
>> >> > /arit-war-0.1
>> >> >
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209
>> >> >
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > Chinmoy
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> >> > <am...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty
>> >> >> <cc...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi All,
>> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >> >>> configured (servlet mappings) in web.xml we get following error in
>> >> >>> Tomcat
>> >> >>> 6.0.24.
>> >> >>> "A web application appears to have started a thread named [Timer-0]
>> >> >>> but
>> >> >>> has failed to stop it. This is very likely to create a memory
>> >> >>> leak".
>> >> >>
>> >> >> Axis2 starts a new timer task to pool the deployment directory.
>> >> >> This
>> >> >> could be this thread.
>> >> >> try switch offing hotUpdate
>> >> >> <parameter name="hotdeployment">false</parameter>
>> >> >>
>> >> >> thanks,
>> >> >> Amila.
>> >> >>>
>> >> >>> According to tomcat developers this happens when an app starts a
>> >> >>> thread
>> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22
>> >> >>> onwards)
>> >> >>> if
>> >> >>> tomcat fails to stop the thread, it gives above message.
>> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
>> >> >>> the
>> >> >>> error.
>> >> >>> Any comments?
>> >> >>> Chinmoy
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Amila Suriarachchi
>> >> >> WSO2 Inc.
>> >> >> blog: http://amilachinthaka.blogspot.com/
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was designed as a module.
Andreas
On Tue, Mar 9, 2010 at 13:35, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> After removing scripting module, the error is gone. Is this bug is fixed in
> Axis2 1.5.1? and what exactly we can do with scripting module?
> Thanks a lot.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> This could be related to AXIS2-4263. Can you try the workaround(s)
>> proposed in that issue?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Andreas,
>> > Following is the report I got after stopping our app:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > <defunct>
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks: labware.util.ResourceMonitor
>> >
>> > labware.util.ResourceMonitor is our class but once I comment out axis2
>> > entries in web.xml I do not get the error.
>> > Chinmoy
>> >
>> >
>> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Chinmoy,
>> >>
>> >> The important test is actually to get the arit report after stopping
>> >> the Axis2 application. This will really show the leaked resources
>> >> (under "<defunct>"). Can you do this and post the result?
>> >>
>> >> Andreas
>> >>
>> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >> > Amila,
>> >> > Still I get the error after switching off following parameter:
>> >> >
>> >> > <parameter name="hotdeployment">false</parameter>
>> >> > <parameter name="hotupdate">false</parameter>
>> >> > Andreas,
>> >> > I get following report when I
>> >> > tried http://localhost:8080/arit-war-0.1/
>> >> > :
>> >> > /arit-war-0.1
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209 (this is our app)
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > I commented out SOAPMonitorService from web.xml but still I get the
>> >> > error.
>> >> > It seems that the problem lies in
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>> >> > At
>> >> > this point both the above mentioned parameters are switched off.
>> >> > Now if I switched on those params I get following report from arit:
>> >> >
>> >> > /arit-war-0.1
>> >> >
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209
>> >> >
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > Chinmoy
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> >> > <am...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty
>> >> >> <cc...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi All,
>> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >> >>> configured (servlet mappings) in web.xml we get following error in
>> >> >>> Tomcat
>> >> >>> 6.0.24.
>> >> >>> "A web application appears to have started a thread named [Timer-0]
>> >> >>> but
>> >> >>> has failed to stop it. This is very likely to create a memory
>> >> >>> leak".
>> >> >>
>> >> >> Axis2 starts a new timer task to pool the deployment directory.
>> >> >> This
>> >> >> could be this thread.
>> >> >> try switch offing hotUpdate
>> >> >> <parameter name="hotdeployment">false</parameter>
>> >> >>
>> >> >> thanks,
>> >> >> Amila.
>> >> >>>
>> >> >>> According to tomcat developers this happens when an app starts a
>> >> >>> thread
>> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22
>> >> >>> onwards)
>> >> >>> if
>> >> >>> tomcat fails to stop the thread, it gives above message.
>> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
>> >> >>> the
>> >> >>> error.
>> >> >>> Any comments?
>> >> >>> Chinmoy
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Amila Suriarachchi
>> >> >> WSO2 Inc.
>> >> >> blog: http://amilachinthaka.blogspot.com/
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
The issue is still open and I can see the same leak with a snapshot
build. The scripting module allows you to deploy Web services
implemented using Javascript and other scripting languages. This
should actually be implemented as a custom deployer, but (for
presumably historical reasons) it was designed as a module.
Andreas
On Tue, Mar 9, 2010 at 13:35, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> After removing scripting module, the error is gone. Is this bug is fixed in
> Axis2 1.5.1? and what exactly we can do with scripting module?
> Thanks a lot.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> This could be related to AXIS2-4263. Can you try the workaround(s)
>> proposed in that issue?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Andreas,
>> > Following is the report I got after stopping our app:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > <defunct>
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks: labware.util.ResourceMonitor
>> >
>> > labware.util.ResourceMonitor is our class but once I comment out axis2
>> > entries in web.xml I do not get the error.
>> > Chinmoy
>> >
>> >
>> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
>> > <an...@gmail.com>
>> > wrote:
>> >>
>> >> Chinmoy,
>> >>
>> >> The important test is actually to get the arit report after stopping
>> >> the Axis2 application. This will really show the leaked resources
>> >> (under "<defunct>"). Can you do this and post the result?
>> >>
>> >> Andreas
>> >>
>> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >> > Amila,
>> >> > Still I get the error after switching off following parameter:
>> >> >
>> >> > <parameter name="hotdeployment">false</parameter>
>> >> > <parameter name="hotupdate">false</parameter>
>> >> > Andreas,
>> >> > I get following report when I
>> >> > tried http://localhost:8080/arit-war-0.1/
>> >> > :
>> >> > /arit-war-0.1
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209 (this is our app)
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > I commented out SOAPMonitorService from web.xml but still I get the
>> >> > error.
>> >> > It seems that the problem lies in
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
>> >> > At
>> >> > this point both the above mentioned parameters are switched off.
>> >> > Now if I switched on those params I get following report from arit:
>> >> >
>> >> > /arit-war-0.1
>> >> >
>> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >> >
>> >> > /web3_dev_1209
>> >> >
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Timer thread; tasks:
>> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> >> > Thread,
>> >> >
>> >> >
>> >> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >> >
>> >> > Chinmoy
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> >> > <am...@gmail.com> wrote:
>> >> >>
>> >> >>
>> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty
>> >> >> <cc...@gmail.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi All,
>> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >> >>> configured (servlet mappings) in web.xml we get following error in
>> >> >>> Tomcat
>> >> >>> 6.0.24.
>> >> >>> "A web application appears to have started a thread named [Timer-0]
>> >> >>> but
>> >> >>> has failed to stop it. This is very likely to create a memory
>> >> >>> leak".
>> >> >>
>> >> >> Axis2 starts a new timer task to pool the deployment directory.
>> >> >> This
>> >> >> could be this thread.
>> >> >> try switch offing hotUpdate
>> >> >> <parameter name="hotdeployment">false</parameter>
>> >> >>
>> >> >> thanks,
>> >> >> Amila.
>> >> >>>
>> >> >>> According to tomcat developers this happens when an app starts a
>> >> >>> thread
>> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22
>> >> >>> onwards)
>> >> >>> if
>> >> >>> tomcat fails to stop the thread, it gives above message.
>> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
>> >> >>> the
>> >> >>> error.
>> >> >>> Any comments?
>> >> >>> Chinmoy
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Amila Suriarachchi
>> >> >> WSO2 Inc.
>> >> >> blog: http://amilachinthaka.blogspot.com/
>> >> >
>> >> >
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> >> For additional commands, e-mail: java-dev-help@axis.apache.org
>> >>
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the workaround(s)
> proposed in that issue?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Andreas,
> > Following is the report I got after stopping our app:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > <defunct>
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks: labware.util.ResourceMonitor
> >
> > labware.util.ResourceMonitor is our class but once I comment out axis2
> > entries in web.xml I do not get the error.
> > Chinmoy
> >
> >
> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Chinmoy,
> >>
> >> The important test is actually to get the arit report after stopping
> >> the Axis2 application. This will really show the leaked resources
> >> (under "<defunct>"). Can you do this and post the result?
> >>
> >> Andreas
> >>
> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >> > Amila,
> >> > Still I get the error after switching off following parameter:
> >> >
> >> > <parameter name="hotdeployment">false</parameter>
> >> > <parameter name="hotupdate">false</parameter>
> >> > Andreas,
> >> > I get following report when I tried
> http://localhost:8080/arit-war-0.1/
> >> > :
> >> > /arit-war-0.1
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209 (this is our app)
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > I commented out SOAPMonitorService from web.xml but still I get the
> >> > error.
> >> > It seems that the problem lies in
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
> At
> >> > this point both the above mentioned parameters are switched off.
> >> > Now if I switched on those params I get following report from arit:
> >> >
> >> > /arit-war-0.1
> >> >
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209
> >> >
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > Chinmoy
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> >> > <am...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <
> cchinu@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi All,
> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >> >>> configured (servlet mappings) in web.xml we get following error in
> >> >>> Tomcat
> >> >>> 6.0.24.
> >> >>> "A web application appears to have started a thread named [Timer-0]
> >> >>> but
> >> >>> has failed to stop it. This is very likely to create a memory leak".
> >> >>
> >> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> >> could be this thread.
> >> >> try switch offing hotUpdate
> >> >> <parameter name="hotdeployment">false</parameter>
> >> >>
> >> >> thanks,
> >> >> Amila.
> >> >>>
> >> >>> According to tomcat developers this happens when an app starts a
> >> >>> thread
> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
> >> >>> if
> >> >>> tomcat fails to stop the thread, it gives above message.
> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
> the
> >> >>> error.
> >> >>> Any comments?
> >> >>> Chinmoy
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Amila Suriarachchi
> >> >> WSO2 Inc.
> >> >> blog: http://amilachinthaka.blogspot.com/
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the workaround(s)
> proposed in that issue?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Andreas,
> > Following is the report I got after stopping our app:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > <defunct>
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks: labware.util.ResourceMonitor
> >
> > labware.util.ResourceMonitor is our class but once I comment out axis2
> > entries in web.xml I do not get the error.
> > Chinmoy
> >
> >
> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Chinmoy,
> >>
> >> The important test is actually to get the arit report after stopping
> >> the Axis2 application. This will really show the leaked resources
> >> (under "<defunct>"). Can you do this and post the result?
> >>
> >> Andreas
> >>
> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >> > Amila,
> >> > Still I get the error after switching off following parameter:
> >> >
> >> > <parameter name="hotdeployment">false</parameter>
> >> > <parameter name="hotupdate">false</parameter>
> >> > Andreas,
> >> > I get following report when I tried
> http://localhost:8080/arit-war-0.1/
> >> > :
> >> > /arit-war-0.1
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209 (this is our app)
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > I commented out SOAPMonitorService from web.xml but still I get the
> >> > error.
> >> > It seems that the problem lies in
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
> At
> >> > this point both the above mentioned parameters are switched off.
> >> > Now if I switched on those params I get following report from arit:
> >> >
> >> > /arit-war-0.1
> >> >
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209
> >> >
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > Chinmoy
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> >> > <am...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <
> cchinu@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi All,
> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >> >>> configured (servlet mappings) in web.xml we get following error in
> >> >>> Tomcat
> >> >>> 6.0.24.
> >> >>> "A web application appears to have started a thread named [Timer-0]
> >> >>> but
> >> >>> has failed to stop it. This is very likely to create a memory leak".
> >> >>
> >> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> >> could be this thread.
> >> >> try switch offing hotUpdate
> >> >> <parameter name="hotdeployment">false</parameter>
> >> >>
> >> >> thanks,
> >> >> Amila.
> >> >>>
> >> >>> According to tomcat developers this happens when an app starts a
> >> >>> thread
> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
> >> >>> if
> >> >>> tomcat fails to stop the thread, it gives above message.
> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
> the
> >> >>> error.
> >> >>> Any comments?
> >> >>> Chinmoy
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Amila Suriarachchi
> >> >> WSO2 Inc.
> >> >> blog: http://amilachinthaka.blogspot.com/
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the workaround(s)
> proposed in that issue?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Andreas,
> > Following is the report I got after stopping our app:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > <defunct>
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks: labware.util.ResourceMonitor
> >
> > labware.util.ResourceMonitor is our class but once I comment out axis2
> > entries in web.xml I do not get the error.
> > Chinmoy
> >
> >
> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Chinmoy,
> >>
> >> The important test is actually to get the arit report after stopping
> >> the Axis2 application. This will really show the leaked resources
> >> (under "<defunct>"). Can you do this and post the result?
> >>
> >> Andreas
> >>
> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >> > Amila,
> >> > Still I get the error after switching off following parameter:
> >> >
> >> > <parameter name="hotdeployment">false</parameter>
> >> > <parameter name="hotupdate">false</parameter>
> >> > Andreas,
> >> > I get following report when I tried
> http://localhost:8080/arit-war-0.1/
> >> > :
> >> > /arit-war-0.1
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209 (this is our app)
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > I commented out SOAPMonitorService from web.xml but still I get the
> >> > error.
> >> > It seems that the problem lies in
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
> At
> >> > this point both the above mentioned parameters are switched off.
> >> > Now if I switched on those params I get following report from arit:
> >> >
> >> > /arit-war-0.1
> >> >
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209
> >> >
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > Chinmoy
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> >> > <am...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <
> cchinu@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi All,
> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >> >>> configured (servlet mappings) in web.xml we get following error in
> >> >>> Tomcat
> >> >>> 6.0.24.
> >> >>> "A web application appears to have started a thread named [Timer-0]
> >> >>> but
> >> >>> has failed to stop it. This is very likely to create a memory leak".
> >> >>
> >> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> >> could be this thread.
> >> >> try switch offing hotUpdate
> >> >> <parameter name="hotdeployment">false</parameter>
> >> >>
> >> >> thanks,
> >> >> Amila.
> >> >>>
> >> >>> According to tomcat developers this happens when an app starts a
> >> >>> thread
> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
> >> >>> if
> >> >>> tomcat fails to stop the thread, it gives above message.
> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
> the
> >> >>> error.
> >> >>> Any comments?
> >> >>> Chinmoy
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Amila Suriarachchi
> >> >> WSO2 Inc.
> >> >> blog: http://amilachinthaka.blogspot.com/
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the workaround(s)
> proposed in that issue?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Andreas,
> > Following is the report I got after stopping our app:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > <defunct>
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks: labware.util.ResourceMonitor
> >
> > labware.util.ResourceMonitor is our class but once I comment out axis2
> > entries in web.xml I do not get the error.
> > Chinmoy
> >
> >
> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Chinmoy,
> >>
> >> The important test is actually to get the arit report after stopping
> >> the Axis2 application. This will really show the leaked resources
> >> (under "<defunct>"). Can you do this and post the result?
> >>
> >> Andreas
> >>
> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >> > Amila,
> >> > Still I get the error after switching off following parameter:
> >> >
> >> > <parameter name="hotdeployment">false</parameter>
> >> > <parameter name="hotupdate">false</parameter>
> >> > Andreas,
> >> > I get following report when I tried
> http://localhost:8080/arit-war-0.1/
> >> > :
> >> > /arit-war-0.1
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209 (this is our app)
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > I commented out SOAPMonitorService from web.xml but still I get the
> >> > error.
> >> > It seems that the problem lies in
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
> At
> >> > this point both the above mentioned parameters are switched off.
> >> > Now if I switched on those params I get following report from arit:
> >> >
> >> > /arit-war-0.1
> >> >
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209
> >> >
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > Chinmoy
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> >> > <am...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <
> cchinu@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi All,
> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >> >>> configured (servlet mappings) in web.xml we get following error in
> >> >>> Tomcat
> >> >>> 6.0.24.
> >> >>> "A web application appears to have started a thread named [Timer-0]
> >> >>> but
> >> >>> has failed to stop it. This is very likely to create a memory leak".
> >> >>
> >> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> >> could be this thread.
> >> >> try switch offing hotUpdate
> >> >> <parameter name="hotdeployment">false</parameter>
> >> >>
> >> >> thanks,
> >> >> Amila.
> >> >>>
> >> >>> According to tomcat developers this happens when an app starts a
> >> >>> thread
> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
> >> >>> if
> >> >>> tomcat fails to stop the thread, it gives above message.
> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
> the
> >> >>> error.
> >> >>> Any comments?
> >> >>> Chinmoy
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Amila Suriarachchi
> >> >> WSO2 Inc.
> >> >> blog: http://amilachinthaka.blogspot.com/
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
After removing scripting module, the error is gone. Is this bug is fixed in
Axis2 1.5.1? and what exactly we can do with scripting module?
Thanks a lot.
Chinmoy
On Tue, Mar 9, 2010 at 5:06 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> This could be related to AXIS2-4263. Can you try the workaround(s)
> proposed in that issue?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Andreas,
> > Following is the report I got after stopping our app:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > <defunct>
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks: labware.util.ResourceMonitor
> >
> > labware.util.ResourceMonitor is our class but once I comment out axis2
> > entries in web.xml I do not get the error.
> > Chinmoy
> >
> >
> > On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <
> andreas.veithen@gmail.com>
> > wrote:
> >>
> >> Chinmoy,
> >>
> >> The important test is actually to get the arit report after stopping
> >> the Axis2 application. This will really show the leaked resources
> >> (under "<defunct>"). Can you do this and post the result?
> >>
> >> Andreas
> >>
> >> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >> > Amila,
> >> > Still I get the error after switching off following parameter:
> >> >
> >> > <parameter name="hotdeployment">false</parameter>
> >> > <parameter name="hotupdate">false</parameter>
> >> > Andreas,
> >> > I get following report when I tried
> http://localhost:8080/arit-war-0.1/
> >> > :
> >> > /arit-war-0.1
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209 (this is our app)
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > I commented out SOAPMonitorService from web.xml but still I get the
> >> > error.
> >> > It seems that the problem lies in
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask .
> At
> >> > this point both the above mentioned parameters are switched off.
> >> > Now if I switched on those params I get following report from arit:
> >> >
> >> > /arit-war-0.1
> >> >
> >> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >> >
> >> > /web3_dev_1209
> >> >
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Timer thread; tasks:
> >> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> >> > Thread,
> >> >
> >> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >> >
> >> > Chinmoy
> >> >
> >> >
> >> >
> >> >
> >> >
> >> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> >> > <am...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <
> cchinu@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi All,
> >> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >> >>> configured (servlet mappings) in web.xml we get following error in
> >> >>> Tomcat
> >> >>> 6.0.24.
> >> >>> "A web application appears to have started a thread named [Timer-0]
> >> >>> but
> >> >>> has failed to stop it. This is very likely to create a memory leak".
> >> >>
> >> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> >> could be this thread.
> >> >> try switch offing hotUpdate
> >> >> <parameter name="hotdeployment">false</parameter>
> >> >>
> >> >> thanks,
> >> >> Amila.
> >> >>>
> >> >>> According to tomcat developers this happens when an app starts a
> >> >>> thread
> >> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
> >> >>> if
> >> >>> tomcat fails to stop the thread, it gives above message.
> >> >>> If we comment out Axis2 servlet mappings in web.xml we do not get
> the
> >> >>> error.
> >> >>> Any comments?
> >> >>> Chinmoy
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Amila Suriarachchi
> >> >> WSO2 Inc.
> >> >> blog: http://amilachinthaka.blogspot.com/
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/
>> > :
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> > error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> >>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> >>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> >>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> >>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/
>> > :
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> > error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> >>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> >>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> >>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> >>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
Chinmoy
On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> - Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> - Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
Chinmoy
On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> - Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> - Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/
>> > :
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> > error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> >>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> >>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> >>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> >>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/
>> > :
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> > error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> >>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> >>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> >>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> >>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
This could be related to AXIS2-4263. Can you try the workaround(s)
proposed in that issue?
Andreas
On Tue, Mar 9, 2010 at 10:46, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Andreas,
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
> Chinmoy
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <an...@gmail.com>
> wrote:
>>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/
>> > :
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> > error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> > target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> >>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> >>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> >>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> >>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
One more observation : Currently I am running tomcat 6.0.24 with jdk 1.6 but
I do not get this error if I use jdk 1.5 with the same version of tomcat. In
the previous report we saw there were two classes under DEFUNCT head and
both the classes extends TimerTask.
Could it be an issue with jdk 1.6 (the implementation of TimerTask)?
Chinmoy
On Tue, Mar 9, 2010 at 3:16 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Andreas,
>
> Following is the report I got after stopping our app:
>
> /arit-war-0.1
>
> - Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> <defunct>
>
> - Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> - Timer thread; tasks: labware.util.ResourceMonitor
>
> labware.util.ResourceMonitor is our class but once I comment out axis2
> entries in web.xml I do not get the error.
>
> Chinmoy
>
>
>
> On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen <andreas.veithen@gmail.com
> > wrote:
>
>> Chinmoy,
>>
>> The important test is actually to get the arit report after stopping
>> the Axis2 application. This will really show the leaked resources
>> (under "<defunct>"). Can you do this and post the result?
>>
>> Andreas
>>
>> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>> > Amila,
>> > Still I get the error after switching off following parameter:
>> >
>> > <parameter name="hotdeployment">false</parameter>
>> > <parameter name="hotupdate">false</parameter>
>> > Andreas,
>> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
>> > /arit-war-0.1
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209 (this is our app)
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > I commented out SOAPMonitorService from web.xml but still I get the
>> error.
>> > It seems that the problem lies in
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
>> > this point both the above mentioned parameters are switched off.
>> > Now if I switched on those params I get following report from arit:
>> >
>> > /arit-war-0.1
>> >
>> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>> >
>> > /web3_dev_1209
>> >
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Timer thread; tasks:
>> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
>> > Thread,
>> >
>> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>> >
>> > Chinmoy
>> >
>> >
>> >
>> >
>> >
>> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
>> > <am...@gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi All,
>> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> >>> configured (servlet mappings) in web.xml we get following error in
>> Tomcat
>> >>> 6.0.24.
>> >>> "A web application appears to have started a thread named [Timer-0]
>> but
>> >>> has failed to stop it. This is very likely to create a memory leak".
>> >>
>> >> Axis2 starts a new timer task to pool the deployment directory. This
>> >> could be this thread.
>> >> try switch offing hotUpdate
>> >> <parameter name="hotdeployment">false</parameter>
>> >>
>> >> thanks,
>> >> Amila.
>> >>>
>> >>> According to tomcat developers this happens when an app starts a
>> thread
>> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards)
>> if
>> >>> tomcat fails to stop the thread, it gives above message.
>> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> >>> error.
>> >>> Any comments?
>> >>> Chinmoy
>> >>
>> >>
>> >>
>> >> --
>> >> Amila Suriarachchi
>> >> WSO2 Inc.
>> >> blog: http://amilachinthaka.blogspot.com/
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>
>>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
<defunct>
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
labware.util.ResourceMonitor is our class but once I comment out axis2
entries in web.xml I do not get the error.
Chinmoy
On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> The important test is actually to get the arit report after stopping
> the Axis2 application. This will really show the leaked resources
> (under "<defunct>"). Can you do this and post the result?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Amila,
> > Still I get the error after switching off following parameter:
> >
> > <parameter name="hotdeployment">false</parameter>
> > <parameter name="hotupdate">false</parameter>
> > Andreas,
> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
> > /arit-war-0.1
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209 (this is our app)
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > I commented out SOAPMonitorService from web.xml but still I get the
> error.
> > It seems that the problem lies in
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> > this point both the above mentioned parameters are switched off.
> > Now if I switched on those params I get following report from arit:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > Chinmoy
> >
> >
> >
> >
> >
> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> >>
> >>
> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >>>
> >>> Hi All,
> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >>> configured (servlet mappings) in web.xml we get following error in
> Tomcat
> >>> 6.0.24.
> >>> "A web application appears to have started a thread named [Timer-0] but
> >>> has failed to stop it. This is very likely to create a memory leak".
> >>
> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> could be this thread.
> >> try switch offing hotUpdate
> >> <parameter name="hotdeployment">false</parameter>
> >>
> >> thanks,
> >> Amila.
> >>>
> >>> According to tomcat developers this happens when an app starts a thread
> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
> >>> tomcat fails to stop the thread, it gives above message.
> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
> >>> error.
> >>> Any comments?
> >>> Chinmoy
> >>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
<defunct>
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
labware.util.ResourceMonitor is our class but once I comment out axis2
entries in web.xml I do not get the error.
Chinmoy
On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> The important test is actually to get the arit report after stopping
> the Axis2 application. This will really show the leaked resources
> (under "<defunct>"). Can you do this and post the result?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Amila,
> > Still I get the error after switching off following parameter:
> >
> > <parameter name="hotdeployment">false</parameter>
> > <parameter name="hotupdate">false</parameter>
> > Andreas,
> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
> > /arit-war-0.1
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209 (this is our app)
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > I commented out SOAPMonitorService from web.xml but still I get the
> error.
> > It seems that the problem lies in
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> > this point both the above mentioned parameters are switched off.
> > Now if I switched on those params I get following report from arit:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > Chinmoy
> >
> >
> >
> >
> >
> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> >>
> >>
> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >>>
> >>> Hi All,
> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >>> configured (servlet mappings) in web.xml we get following error in
> Tomcat
> >>> 6.0.24.
> >>> "A web application appears to have started a thread named [Timer-0] but
> >>> has failed to stop it. This is very likely to create a memory leak".
> >>
> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> could be this thread.
> >> try switch offing hotUpdate
> >> <parameter name="hotdeployment">false</parameter>
> >>
> >> thanks,
> >> Amila.
> >>>
> >>> According to tomcat developers this happens when an app starts a thread
> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
> >>> tomcat fails to stop the thread, it gives above message.
> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
> >>> error.
> >>> Any comments?
> >>> Chinmoy
> >>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
<defunct>
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
labware.util.ResourceMonitor is our class but once I comment out axis2
entries in web.xml I do not get the error.
Chinmoy
On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> The important test is actually to get the arit report after stopping
> the Axis2 application. This will really show the leaked resources
> (under "<defunct>"). Can you do this and post the result?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Amila,
> > Still I get the error after switching off following parameter:
> >
> > <parameter name="hotdeployment">false</parameter>
> > <parameter name="hotupdate">false</parameter>
> > Andreas,
> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
> > /arit-war-0.1
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209 (this is our app)
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > I commented out SOAPMonitorService from web.xml but still I get the
> error.
> > It seems that the problem lies in
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> > this point both the above mentioned parameters are switched off.
> > Now if I switched on those params I get following report from arit:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > Chinmoy
> >
> >
> >
> >
> >
> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> >>
> >>
> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >>>
> >>> Hi All,
> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >>> configured (servlet mappings) in web.xml we get following error in
> Tomcat
> >>> 6.0.24.
> >>> "A web application appears to have started a thread named [Timer-0] but
> >>> has failed to stop it. This is very likely to create a memory leak".
> >>
> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> could be this thread.
> >> try switch offing hotUpdate
> >> <parameter name="hotdeployment">false</parameter>
> >>
> >> thanks,
> >> Amila.
> >>>
> >>> According to tomcat developers this happens when an app starts a thread
> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
> >>> tomcat fails to stop the thread, it gives above message.
> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
> >>> error.
> >>> Any comments?
> >>> Chinmoy
> >>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
<defunct>
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
labware.util.ResourceMonitor is our class but once I comment out axis2
entries in web.xml I do not get the error.
Chinmoy
On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> The important test is actually to get the arit report after stopping
> the Axis2 application. This will really show the leaked resources
> (under "<defunct>"). Can you do this and post the result?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Amila,
> > Still I get the error after switching off following parameter:
> >
> > <parameter name="hotdeployment">false</parameter>
> > <parameter name="hotupdate">false</parameter>
> > Andreas,
> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
> > /arit-war-0.1
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209 (this is our app)
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > I commented out SOAPMonitorService from web.xml but still I get the
> error.
> > It seems that the problem lies in
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> > this point both the above mentioned parameters are switched off.
> > Now if I switched on those params I get following report from arit:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > Chinmoy
> >
> >
> >
> >
> >
> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> >>
> >>
> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >>>
> >>> Hi All,
> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >>> configured (servlet mappings) in web.xml we get following error in
> Tomcat
> >>> 6.0.24.
> >>> "A web application appears to have started a thread named [Timer-0] but
> >>> has failed to stop it. This is very likely to create a memory leak".
> >>
> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> could be this thread.
> >> try switch offing hotUpdate
> >> <parameter name="hotdeployment">false</parameter>
> >>
> >> thanks,
> >> Amila.
> >>>
> >>> According to tomcat developers this happens when an app starts a thread
> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
> >>> tomcat fails to stop the thread, it gives above message.
> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
> >>> error.
> >>> Any comments?
> >>> Chinmoy
> >>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Andreas,
Following is the report I got after stopping our app:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
<defunct>
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks: labware.util.ResourceMonitor
labware.util.ResourceMonitor is our class but once I comment out axis2
entries in web.xml I do not get the error.
Chinmoy
On Tue, Mar 9, 2010 at 3:05 PM, Andreas Veithen
<an...@gmail.com>wrote:
> Chinmoy,
>
> The important test is actually to get the arit report after stopping
> the Axis2 application. This will really show the leaked resources
> (under "<defunct>"). Can you do this and post the result?
>
> Andreas
>
> On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com>
> wrote:
> > Amila,
> > Still I get the error after switching off following parameter:
> >
> > <parameter name="hotdeployment">false</parameter>
> > <parameter name="hotupdate">false</parameter>
> > Andreas,
> > I get following report when I tried http://localhost:8080/arit-war-0.1/:
> > /arit-war-0.1
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209 (this is our app)
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > I commented out SOAPMonitorService from web.xml but still I get the
> error.
> > It seems that the problem lies in
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> > this point both the above mentioned parameters are switched off.
> > Now if I switched on those params I get following report from arit:
> >
> > /arit-war-0.1
> >
> > Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
> >
> > /web3_dev_1209
> >
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Timer thread; tasks:
> > org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> > Thread,
> >
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
> >
> > Chinmoy
> >
> >
> >
> >
> >
> > On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> > <am...@gmail.com> wrote:
> >>
> >>
> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
> >> wrote:
> >>>
> >>> Hi All,
> >>> I have an application which uses Axis2 1.4.1. When we have Axis2
> >>> configured (servlet mappings) in web.xml we get following error in
> Tomcat
> >>> 6.0.24.
> >>> "A web application appears to have started a thread named [Timer-0] but
> >>> has failed to stop it. This is very likely to create a memory leak".
> >>
> >> Axis2 starts a new timer task to pool the deployment directory. This
> >> could be this thread.
> >> try switch offing hotUpdate
> >> <parameter name="hotdeployment">false</parameter>
> >>
> >> thanks,
> >> Amila.
> >>>
> >>> According to tomcat developers this happens when an app starts a thread
> >>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
> >>> tomcat fails to stop the thread, it gives above message.
> >>> If we comment out Axis2 servlet mappings in web.xml we do not get the
> >>> error.
> >>> Any comments?
> >>> Chinmoy
> >>
> >>
> >>
> >> --
> >> Amila Suriarachchi
> >> WSO2 Inc.
> >> blog: http://amilachinthaka.blogspot.com/
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under "<defunct>"). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Amila,
> Still I get the error after switching off following parameter:
>
> <parameter name="hotdeployment">false</parameter>
> <parameter name="hotupdate">false</parameter>
> Andreas,
> I get following report when I tried http://localhost:8080/arit-war-0.1/ :
> /arit-war-0.1
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209 (this is our app)
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> I commented out SOAPMonitorService from web.xml but still I get the error.
> It seems that the problem lies in
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> this point both the above mentioned parameters are switched off.
> Now if I switched on those params I get following report from arit:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> Chinmoy
>
>
>
>
>
> On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>>>
>>> Hi All,
>>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> configured (servlet mappings) in web.xml we get following error in Tomcat
>>> 6.0.24.
>>> "A web application appears to have started a thread named [Timer-0] but
>>> has failed to stop it. This is very likely to create a memory leak".
>>
>> Axis2 starts a new timer task to pool the deployment directory. This
>> could be this thread.
>> try switch offing hotUpdate
>> <parameter name="hotdeployment">false</parameter>
>>
>> thanks,
>> Amila.
>>>
>>> According to tomcat developers this happens when an app starts a thread
>>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>>> tomcat fails to stop the thread, it gives above message.
>>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> error.
>>> Any comments?
>>> Chinmoy
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under "<defunct>"). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Amila,
> Still I get the error after switching off following parameter:
>
> <parameter name="hotdeployment">false</parameter>
> <parameter name="hotupdate">false</parameter>
> Andreas,
> I get following report when I tried http://localhost:8080/arit-war-0.1/ :
> /arit-war-0.1
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209 (this is our app)
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> I commented out SOAPMonitorService from web.xml but still I get the error.
> It seems that the problem lies in
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> this point both the above mentioned parameters are switched off.
> Now if I switched on those params I get following report from arit:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> Chinmoy
>
>
>
>
>
> On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>>>
>>> Hi All,
>>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> configured (servlet mappings) in web.xml we get following error in Tomcat
>>> 6.0.24.
>>> "A web application appears to have started a thread named [Timer-0] but
>>> has failed to stop it. This is very likely to create a memory leak".
>>
>> Axis2 starts a new timer task to pool the deployment directory. This
>> could be this thread.
>> try switch offing hotUpdate
>> <parameter name="hotdeployment">false</parameter>
>>
>> thanks,
>> Amila.
>>>
>>> According to tomcat developers this happens when an app starts a thread
>>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>>> tomcat fails to stop the thread, it gives above message.
>>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> error.
>>> Any comments?
>>> Chinmoy
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under "<defunct>"). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Amila,
> Still I get the error after switching off following parameter:
>
> <parameter name="hotdeployment">false</parameter>
> <parameter name="hotupdate">false</parameter>
> Andreas,
> I get following report when I tried http://localhost:8080/arit-war-0.1/ :
> /arit-war-0.1
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209 (this is our app)
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> I commented out SOAPMonitorService from web.xml but still I get the error.
> It seems that the problem lies in
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> this point both the above mentioned parameters are switched off.
> Now if I switched on those params I get following report from arit:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> Chinmoy
>
>
>
>
>
> On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>>>
>>> Hi All,
>>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> configured (servlet mappings) in web.xml we get following error in Tomcat
>>> 6.0.24.
>>> "A web application appears to have started a thread named [Timer-0] but
>>> has failed to stop it. This is very likely to create a memory leak".
>>
>> Axis2 starts a new timer task to pool the deployment directory. This
>> could be this thread.
>> try switch offing hotUpdate
>> <parameter name="hotdeployment">false</parameter>
>>
>> thanks,
>> Amila.
>>>
>>> According to tomcat developers this happens when an app starts a thread
>>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>>> tomcat fails to stop the thread, it gives above message.
>>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> error.
>>> Any comments?
>>> Chinmoy
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under "<defunct>"). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Amila,
> Still I get the error after switching off following parameter:
>
> <parameter name="hotdeployment">false</parameter>
> <parameter name="hotupdate">false</parameter>
> Andreas,
> I get following report when I tried http://localhost:8080/arit-war-0.1/ :
> /arit-war-0.1
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209 (this is our app)
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> I commented out SOAPMonitorService from web.xml but still I get the error.
> It seems that the problem lies in
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> this point both the above mentioned parameters are switched off.
> Now if I switched on those params I get following report from arit:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> Chinmoy
>
>
>
>
>
> On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>>>
>>> Hi All,
>>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> configured (servlet mappings) in web.xml we get following error in Tomcat
>>> 6.0.24.
>>> "A web application appears to have started a thread named [Timer-0] but
>>> has failed to stop it. This is very likely to create a memory leak".
>>
>> Axis2 starts a new timer task to pool the deployment directory. This
>> could be this thread.
>> try switch offing hotUpdate
>> <parameter name="hotdeployment">false</parameter>
>>
>> thanks,
>> Amila.
>>>
>>> According to tomcat developers this happens when an app starts a thread
>>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>>> tomcat fails to stop the thread, it gives above message.
>>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> error.
>>> Any comments?
>>> Chinmoy
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
The important test is actually to get the arit report after stopping
the Axis2 application. This will really show the leaked resources
(under "<defunct>"). Can you do this and post the result?
Andreas
On Tue, Mar 9, 2010 at 10:27, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Amila,
> Still I get the error after switching off following parameter:
>
> <parameter name="hotdeployment">false</parameter>
> <parameter name="hotupdate">false</parameter>
> Andreas,
> I get following report when I tried http://localhost:8080/arit-war-0.1/ :
> /arit-war-0.1
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209 (this is our app)
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> I commented out SOAPMonitorService from web.xml but still I get the error.
> It seems that the problem lies in
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
> this point both the above mentioned parameters are switched off.
> Now if I switched on those params I get following report from arit:
>
> /arit-war-0.1
>
> Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
>
> /web3_dev_1209
>
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Timer thread; tasks:
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
> Thread,
> target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
>
> Chinmoy
>
>
>
>
>
> On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi
> <am...@gmail.com> wrote:
>>
>>
>> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>
>> wrote:
>>>
>>> Hi All,
>>> I have an application which uses Axis2 1.4.1. When we have Axis2
>>> configured (servlet mappings) in web.xml we get following error in Tomcat
>>> 6.0.24.
>>> "A web application appears to have started a thread named [Timer-0] but
>>> has failed to stop it. This is very likely to create a memory leak".
>>
>> Axis2 starts a new timer task to pool the deployment directory. This
>> could be this thread.
>> try switch offing hotUpdate
>> <parameter name="hotdeployment">false</parameter>
>>
>> thanks,
>> Amila.
>>>
>>> According to tomcat developers this happens when an app starts a thread
>>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>>> tomcat fails to stop the thread, it gives above message.
>>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>>> error.
>>> Any comments?
>>> Chinmoy
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Amila,
Still I get the error after switching off following parameter:
<parameter name="hotdeployment">false</parameter>
<parameter name="hotupdate">false</parameter>
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
I commented out SOAPMonitorService from web.xml but still I get the error.
It seems that the problem lies in
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
this point both the above mentioned parameters are switched off.
Now if I switched on those params I get following report from arit:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
Chinmoy
On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Hi All,
>>
>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> configured (servlet mappings) in web.xml we get following error in Tomcat
>> 6.0.24.
>>
>> "*A web application appears to have started a thread named [Timer-0] but
>> has failed to stop it. This is very likely to create a memory leak*".
>
>
> Axis2 starts a new timer task to pool the deployment directory. This could
> be this thread.
> try switch offing hotUpdate
> <parameter name="hotdeployment">false</parameter>
>
> thanks,
> Amila.
>
>>
>> According to tomcat developers this happens when an app starts a thread
>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>> tomcat fails to stop the thread, it gives above message.
>>
>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> error.
>>
>> Any comments?
>>
>> Chinmoy
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Amila,
Still I get the error after switching off following parameter:
<parameter name="hotdeployment">false</parameter>
<parameter name="hotupdate">false</parameter>
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
I commented out SOAPMonitorService from web.xml but still I get the error.
It seems that the problem lies in
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
this point both the above mentioned parameters are switched off.
Now if I switched on those params I get following report from arit:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
Chinmoy
On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Hi All,
>>
>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> configured (servlet mappings) in web.xml we get following error in Tomcat
>> 6.0.24.
>>
>> "*A web application appears to have started a thread named [Timer-0] but
>> has failed to stop it. This is very likely to create a memory leak*".
>
>
> Axis2 starts a new timer task to pool the deployment directory. This could
> be this thread.
> try switch offing hotUpdate
> <parameter name="hotdeployment">false</parameter>
>
> thanks,
> Amila.
>
>>
>> According to tomcat developers this happens when an app starts a thread
>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>> tomcat fails to stop the thread, it gives above message.
>>
>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> error.
>>
>> Any comments?
>>
>> Chinmoy
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Amila,
Still I get the error after switching off following parameter:
<parameter name="hotdeployment">false</parameter>
<parameter name="hotupdate">false</parameter>
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
I commented out SOAPMonitorService from web.xml but still I get the error.
It seems that the problem lies in
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
this point both the above mentioned parameters are switched off.
Now if I switched on those params I get following report from arit:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
Chinmoy
On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Hi All,
>>
>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> configured (servlet mappings) in web.xml we get following error in Tomcat
>> 6.0.24.
>>
>> "*A web application appears to have started a thread named [Timer-0] but
>> has failed to stop it. This is very likely to create a memory leak*".
>
>
> Axis2 starts a new timer task to pool the deployment directory. This could
> be this thread.
> try switch offing hotUpdate
> <parameter name="hotdeployment">false</parameter>
>
> thanks,
> Amila.
>
>>
>> According to tomcat developers this happens when an app starts a thread
>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>> tomcat fails to stop the thread, it gives above message.
>>
>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> error.
>>
>> Any comments?
>>
>> Chinmoy
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Amila,
Still I get the error after switching off following parameter:
<parameter name="hotdeployment">false</parameter>
<parameter name="hotupdate">false</parameter>
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
I commented out SOAPMonitorService from web.xml but still I get the error.
It seems that the problem lies in
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
this point both the above mentioned parameters are switched off.
Now if I switched on those params I get following report from arit:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
Chinmoy
On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Hi All,
>>
>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> configured (servlet mappings) in web.xml we get following error in Tomcat
>> 6.0.24.
>>
>> "*A web application appears to have started a thread named [Timer-0] but
>> has failed to stop it. This is very likely to create a memory leak*".
>
>
> Axis2 starts a new timer task to pool the deployment directory. This could
> be this thread.
> try switch offing hotUpdate
> <parameter name="hotdeployment">false</parameter>
>
> thanks,
> Amila.
>
>>
>> According to tomcat developers this happens when an app starts a thread
>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>> tomcat fails to stop the thread, it gives above message.
>>
>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> error.
>>
>> Any comments?
>>
>> Chinmoy
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Chinmoy Chakraborty <cc...@gmail.com>.
Amila,
Still I get the error after switching off following parameter:
<parameter name="hotdeployment">false</parameter>
<parameter name="hotupdate">false</parameter>
Andreas,
I get following report when I tried *http://localhost:8080/arit-war-0.1/* :
/arit-war-0.1
Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209 (this is our app)
Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
I commented out SOAPMonitorService from web.xml but still I get the error.
It seems that the problem lies in
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask . At
this point both the above mentioned parameters are switched off.
Now if I switched on those params I get following report from arit:
/arit-war-0.1
- Thread, target=org.apache.tomcat.util.net.AprEndpoint$Worker
/web3_dev_1209
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Timer thread; tasks:
org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask
- Thread,
target=org.apache.axis2.soapmonitor.servlet.SOAPMonitorService$ServerSocketThread
Chinmoy
On Tue, Mar 9, 2010 at 10:32 AM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
>
>> Hi All,
>>
>> I have an application which uses Axis2 1.4.1. When we have Axis2
>> configured (servlet mappings) in web.xml we get following error in Tomcat
>> 6.0.24.
>>
>> "*A web application appears to have started a thread named [Timer-0] but
>> has failed to stop it. This is very likely to create a memory leak*".
>
>
> Axis2 starts a new timer task to pool the deployment directory. This could
> be this thread.
> try switch offing hotUpdate
> <parameter name="hotdeployment">false</parameter>
>
> thanks,
> Amila.
>
>>
>> According to tomcat developers this happens when an app starts a thread
>> but never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if
>> tomcat fails to stop the thread, it gives above message.
>>
>> If we comment out Axis2 servlet mappings in web.xml we do not get the
>> error.
>>
>> Any comments?
>>
>> Chinmoy
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
Re: Possible memory leak in Axis2 1.4.1?
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Hi All,
>
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
>
> "*A web application appears to have started a thread named [Timer-0] but
> has failed to stop it. This is very likely to create a memory leak*".
Axis2 starts a new timer task to pool the deployment directory. This could
be this thread.
try switch offing hotUpdate
<parameter name="hotdeployment">false</parameter>
thanks,
Amila.
>
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
>
> If we comment out Axis2 servlet mappings in web.xml we do not get the
> error.
>
> Any comments?
>
> Chinmoy
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Hi All,
>
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
>
> "*A web application appears to have started a thread named [Timer-0] but
> has failed to stop it. This is very likely to create a memory leak*".
Axis2 starts a new timer task to pool the deployment directory. This could
be this thread.
try switch offing hotUpdate
<parameter name="hotdeployment">false</parameter>
thanks,
Amila.
>
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
>
> If we comment out Axis2 servlet mappings in web.xml we do not get the
> error.
>
> Any comments?
>
> Chinmoy
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Possible memory leak in Axis2 1.4.1?
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Hi All,
>
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
>
> "*A web application appears to have started a thread named [Timer-0] but
> has failed to stop it. This is very likely to create a memory leak*".
Axis2 starts a new timer task to pool the deployment directory. This could
be this thread.
try switch offing hotUpdate
<parameter name="hotdeployment">false</parameter>
thanks,
Amila.
>
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
>
> If we comment out Axis2 servlet mappings in web.xml we do not get the
> error.
>
> Any comments?
>
> Chinmoy
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Hi All,
>
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
>
> "*A web application appears to have started a thread named [Timer-0] but
> has failed to stop it. This is very likely to create a memory leak*".
Axis2 starts a new timer task to pool the deployment directory. This could
be this thread.
try switch offing hotUpdate
<parameter name="hotdeployment">false</parameter>
thanks,
Amila.
>
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
>
> If we comment out Axis2 servlet mappings in web.xml we do not get the
> error.
>
> Any comments?
>
> Chinmoy
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
Re: Possible memory leak in Axis2 1.4.1?
Posted by Amila Suriarachchi <am...@gmail.com>.
On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty <cc...@gmail.com>wrote:
> Hi All,
>
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
>
> "*A web application appears to have started a thread named [Timer-0] but
> has failed to stop it. This is very likely to create a memory leak*".
Axis2 starts a new timer task to pool the deployment directory. This could
be this thread.
try switch offing hotUpdate
<parameter name="hotdeployment">false</parameter>
thanks,
Amila.
>
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
>
> If we comment out Axis2 servlet mappings in web.xml we do not get the
> error.
>
> Any comments?
>
> Chinmoy
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: Possible memory leak in Axis2 1.4.1?
Posted by Andreas Veithen <an...@gmail.com>.
Chinmoy,
In order to figure out where this comes from, can you execute the
following steps?
1. Deploy the arit tool from [1] into the Tomcat instance where Axis2
is deployed.
2. Make sure that both Axis2 and arit are started.
3. Get the report from arit by accessing the context root of the
application (http://localhost:8080/arit-war-1.0).
4. Stop the Axis2 application.
5. Get the report from arit again.
By comparing the reports from 3 and 5, we should be able to get more
information about the leaking timer.
Andreas
[1] http://code.google.com/p/arit/downloads/list
On Mon, Mar 8, 2010 at 16:25, Chinmoy Chakraborty <cc...@gmail.com> wrote:
> Hi All,
> I have an application which uses Axis2 1.4.1. When we have Axis2 configured
> (servlet mappings) in web.xml we get following error in Tomcat 6.0.24.
> "A web application appears to have started a thread named [Timer-0] but has
> failed to stop it. This is very likely to create a memory leak".
> According to tomcat developers this happens when an app starts a thread but
> never stops it. Tomcat tries to stop the thread (6.0.22 onwards) if tomcat
> fails to stop the thread, it gives above message.
> If we comment out Axis2 servlet mappings in web.xml we do not get the error.
> Any comments?
> Chinmoy
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org