Does the Java VM consistently garbage-collect classloaders and classes? Having observed the behaviour of various IDE´s and other Java programs that deal with the issue of dynamically loading byte code, I´m not sure about this at all. If yes, the OOM-situation caused by hot-deployment is indeed a bug.
CGJ -----Ursprüngliche Nachricht----- Von: Scott M Stark [mailto:[EMAIL PROTECTED]] Gesendet: Sonntag, 18. November 2001 00:41 An: [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] Bug #482875: Out of Memory It is a bug, its just a question of its priority. The deployment code is getting old and crusty and needs to be redone. However, since it works well enough in the absence of multiple redeploys its not high on my priority list. The implicit assumption that hot deployment should not be used in production environments is really a criticism of the state of the hot deployment facility. It should be up to the user to make the decision as to whether hot deployment is enabled for a production environment. If I'm running an ASP environment where users can create stores and dynamically update their content then I am going to want some hot deploy feature. Right now were saying don't use ours. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Andreas Schaefer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 17, 2001 1:58 PM Subject: [JBoss-dev] Bug #482875: Out of Memory > Hi Geeks > > Recently this bug was reported on JBoss 2.4 stating that > JBoss server runs out of memory when to many hot- > deployment with big archives. > > IMO this is not a bug because when people start to deploy > big archives then they have to deal with it. > - In Production this should not become a problem and when > then a restart of JBoss is necessary > - In Development this should not be a big problem to bounce > the server. > > What do you think ? > > ------------------------------------------------------------ > > Bugs item #482875, was opened at 2001-11-17 12:12 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=376685&aid=482875&group_id= > 22866 > > Category: JBossServer > Group: v2.4 (stable) > Status: Open > Resolution: None > Priority: 7 > Submitted By: Joel Boehland (jolby) > Assigned to: Nobody/Anonymous (nobody) > Summary: OutOfMemory after many Deploy cycles > > Initial Comment: > I have been seeing OutOfMemoryErrors in my server after > doing several deploy/redeploy cycles of my application > .ear file (which is around 3 megs in size) > > Basic info: > *Hardware: AMD-K2-400MHz, 196MB RAM > *OS: linux 2.2.14 > *jdk: Blackdown-1.3.0-FCS, mixed mode > *Server: JBoss-2.4.3_Jetty-3.1.3-1 > *ServerTrace: I don't have one now, but I can provide > one later if needed. > *Steps to reproduce: Deploy/Redeploy .ear file many > times. My .ear is around 3 megs, so it may be necessary > to use a large one to trigger this effect. > > Other info > *I have had this happen using native threads mode, and > green threads mode. > *"Jozsa Kristof" <[EMAIL PROTECTED]> has also reported > this error on the jboss-user list. He was using IBM jdk > 1.3.0 on linux, so this doesn't appear to be tied to > any particular version of the jdk. > > --Joel > > ----------------------------------------------------------- > > xxxxxxxxxxxxxxxxx > Andreas Schaefer > Senior Consultant > JBoss Group, LLC > xxxxxxxxxxxxxxxxx > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
