[ http://issues.apache.org/jira/browse/AXIS2-595?page=comments#action_12375827 ]
Jens Schumann commented on AXIS2-595: ------------------------------------- Just turned on yourkit today. It's pretty obvious that axis2 prevents reclaiming allocated memory by holding references to the web app classloader (tomcat 5.5.16). If you look at the current axis2 code its seems clear: there are a number of hard references to this webapp classloader (e.g DeploymentEngine), which might be hold by instances of SchedulerTimerTask. > Redeploying axis2.war - OutOfMemory in PermGen space > ---------------------------------------------------- > > Key: AXIS2-595 > URL: http://issues.apache.org/jira/browse/AXIS2-595 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Components: deployment > Environment: JBoss 4.0.4RC1 , OS X Java 1.5.0_06-112 > Reporter: Jens Schumann > Attachments: gc-load-on-startup-disabled.log, gc.log > > Since I have been playing around with axis2.war last days I have noticed that > I do run into an OutOfMemory after a certain number of hot redeployments. > Although JBoss isn't known for releasing all resources during redeploy it is > interesting to see that this happens in PermGen space. Could it be that the > custom .aar/.mar deployment does not release all loaded resources? > 00:07:47,816 ERROR [[/axis2]] StandardWrapper.Throwable > java.lang.OutOfMemoryError: PermGen space > 00:07:47,820 ERROR [[/axis2]] Servlet /axis2 threw load() exception > java.lang.OutOfMemoryError: PermGen space -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
