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 <cch...@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 <andreas.veit...@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 <cch...@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.veit...@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 <cch...@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 >> >> > <amilasuriarach...@gmail.com> wrote: >> >> >> >> >> >> >> >> >> On Mon, Mar 8, 2010 at 8:55 PM, Chinmoy Chakraborty >> >> >> <cch...@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-unsubscr...@axis.apache.org >> >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
