[ http://issues.apache.org/jira/browse/AXIS2-595?page=all ]
Jens Schumann updated AXIS2-595:
--------------------------------
Attachment: gc.log
Thanks for the comment.
Indeed this could be an JBoss UnifiedClassloaderXX issue. Nevertheless I just
tested stock tomcat (5.5.16) and redployed axis2.war a couple times using the
build-in manager app. See attached gc log. Every redeploy will cause a Full GC
and increase the current Perm Gen size until Tomcat just dies (VM is using full
GC all the time).
I don't have time to run this through a profiler till middle of next. For
development purposes this looks like a critical issue to me
> 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.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
