[
https://issues.apache.org/jira/browse/AXIS2-5310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-5310.
------------------------------------
Resolution: Not A Problem
The conclusion given in the description is not correct. Please note that it
says "probable memory leak". Tomcat's leak detector is far from perfect. In
this case:
1. org.apache.axiom.util.UIDGenerator$1 doesn't cause a class loader leak
because the value of that thread local is of type long[]. See
http://code.google.com/p/arit/wiki/ThreadLocal for more information. Note that
previous Axiom versions indeed caused a class loader leak, but this has been
fixed; see AXIOM-354.
2. The thread local storing the org.apache.axis2.context.MessageContext is
cleared when the request has been processed. This doesn't occur because as
shown by the previous error message, "The web application [...] is still
processing a request that has yet to finish". This is generally caused by bugs
in application code, not in Axis2. If you believe that there is an issue in
Axis2 blocking the request, then you need to provide a thread dump that shows
this.
> Axis2.0 : 1.6.2 : Memory Leak Issue
> ------------------------------------
>
> Key: AXIS2-5310
> URL: https://issues.apache.org/jira/browse/AXIS2-5310
> Project: Axis2
> Issue Type: Bug
> Components: databinding, transports
> Affects Versions: 1.6.2
> Environment: Axis2.0 version used : 1.6.2
> NSJSP7.0 and ITP webserver 7.2 for HP Nonstop Tandem
> Reporter: Santhosh
> Labels: Memory, leak, performance
> Original Estimate: 972h
> Remaining Estimate: 972h
>
> I'm facing below error message after deploying a webservice using Axis2.0 in
> webserver.
> Mon, Apr 30, 16:08:27;$Z0QF;INFO;StandardService#stopInternal;Stopping
> service NSJSP
> Mon, Apr 30,
> 16:08:29;$Z0QF;SEVERE;WebappClassLoader#clearReferencesThreads;The web
> application [/PSAPI-V1-0/axis2] is still processing a request that has yet to
> finish. This is very likely to create a memory leak. You can control the time
> allowed for requests to finish by using the unloadDelay attribute of the
> standard Context implementation.
> Mon, Apr 30,
> 16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web
> application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type
> [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@2465e5]) and a value of
> type [org.apache.axis2.context.MessageContext] (value [[MessageContext:
> logID=3fecb85757bee1e6fd9cdc8eb6a0e146d5c1eaa7dd28d0e7]]) but failed to
> remove it when the web application was stopped. Threads are going to be
> renewed over time to try and avoid a probable memory leak.
> Mon, Apr 30,
> 16:08:29;$Z0QF;SEVERE;WebappClassLoader#checkThreadLocalMapForLeaks;The web
> application [/PSAPI-V1-0/axis2] created a ThreadLocal with key of type
> [org.apache.axiom.util.UIDGenerator$1] (value
> [org.apache.axiom.util.UIDGenerator$1@b103dd]) and a value of type [long[]]
> (value [[J@174d4c9]) but failed to remove it when the web application was
> stopped. Threads are going to be renewed over time to try and avoid a
> probable memory leak.
> Mon, Apr 30, 16:08:29;$Z0QF;INFO;AbstractProtocolHandler#stop;Stopping
> ProtocolHandler ["http-bio-0"]
> As per error logs i understand that "Axis2.0 - framework" is not able to
> delete/failed to cleanup a thread. Please provide me with resolution if any.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
