[JBoss-dev] [ jboss-Bugs-435958 ] Out of Memory eception after many redepl

[SourceForge.net <no...@so...>]

Bugs item #435958, was opened at 2001-06-24 21:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=435958&group_id=22866

Category: JBossServer
Group: v2.2.2 (stable)
Status: Closed
Resolution: Rejected
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Andreas Schaefer (schaefera)
Summary: Out of Memory eception after many redepl

Initial Comment:
This behavior has been observed on Windows 2000 SP2, 
running Sun JDK 1.3.1 and jBoss2.2.2 both Tomcat and 
Jetty bundles.

After many EAR hot redeployments in a short period of 
time, (prehaps one every 5 to 20 minutes over a period 
of 6 hours) a redeployment will result in "Out of 
Memory" exceptions being thrown. 

This happens with both the Tomcat and Jetty bundles, 
but the error is much more clear with Jetty. In the 
case of Tomcat, it appears to redeploy correctly but 
creates a variety of errors when the app is run.



----------------------------------------------------------------------

Comment By: Tim McCune (javajedi)
Date: 2003-03-17 17:07

Message:
Logged In: YES 
user_id=62441

This is still happening.  See
http://jboss.org/forums/thread.jsp?forum=121&thread=27888
Can you please reopen this bug?

----------------------------------------------------------------------

Comment By: Andreas Schaefer (schaefera)
Date: 2001-10-29 21:07

Message:
Logged In: YES 
user_id=70434

Need more information about what is deployed. Unfortunately 
memory is always limited and therefore hot deployment will 
one time reach a limit because all the loaded classes are 
not removed from the classloaders.
But to see where a problem is I have to know what is 
deployed and maybe a error stack trace.

----------------------------------------------------------------------

Comment By: Andreas Schaefer (schaefera)
Date: 2001-10-29 21:03

Message:
Logged In: YES 
user_id=70434

Need more information about what is deployed. Unfortunately 
memory is always limited and therefore hot deployment will 
one time reach a limit because all the loaded classes are 
not removed from the classloaders.
But to see where a problem is I have to know what is 
deployed and maybe a error stack trace.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=435958&group_id=22866