This content has been marked as final.
Show 4 replies
-
1. Re: Class leakage on redeployment
raja05 Aug 26, 2006 8:48 AM (in response to ngolovin)Yeah, it throws a OOME -- PermGen Space Filled errors after some 10 - 15 redeployments. I had a read at the Resin site that it could be due to Debuggers if any , and I use a fair amount of debugging with IDE, so I thought that could lead to this, but yeah I get this error too.
-
2. Re: Class leakage on redeployment
smokingapipe Aug 26, 2006 8:38 PM (in response to ngolovin)I experience exactly the same thing. I guess that's ok on my development box, but on my production box, I kill and restart JBoss, unless someone can suggest a way to avoid this leak.
Is there something that is preventing the classloader from being GC'ed? Or is this a problem with the JVM? Because it should be perfectly possible to GC a classloader. -
3. Re: Class leakage on redeployment
ssilvert Aug 27, 2006 9:34 PM (in response to ngolovin)"SmokingAPipe" wrote:
I experience exactly the same thing. I guess that's ok on my development box, but on my production box, I kill and restart JBoss, unless someone can suggest a way to avoid this leak.
Is there something that is preventing the classloader from being GC'ed? Or is this a problem with the JVM? Because it should be perfectly possible to GC a classloader.
It shouldn't leak in JBoss. If you have a step-by-step way to reproduce the problem, please open a Jira task and post a link to it here.
Thanks,
Stan -
4. Re: Class leakage on redeployment
marcioendo Aug 28, 2006 4:37 PM (in response to ngolovin)This is a known issue not directly related to SEAM but to EJB3:
http://jira.jboss.com/jira/browse/JBAS-3071