Bugs item #567381, was opened at 2002-06-11 05:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=567381&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Simon Stewart (shs96c) Assigned to: Nobody/Anonymous (nobody) Summary: Multiple hot-redploys cause JVM panic Initial Comment: Using Sun's JDK 1.4 and the final release of both JBoss 3.0+Jetty and JBoss 3.0+catalina attempting to redeploy an app numerous times will eventually cause the JVM to panic. I've not tested this with a proper EAR file, but on a set of exploded directories. Having said this, from the nature of the problem, I don't think that's the cause. Technical information: JDK 1.4 (from Sun) Debian Linux (latest testing) with 2.2.17 kernel JBoss 3.0.0 final Steps required to reproduce: 1) Start JBoss as normal and deploy an app. 2) Make a change to one of the files and touch application.xml 3) Wait until JBoss has redeployed the app. 4) Repeat steps 2 to 4 ;) ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2002-06-15 17:59 Message: Logged In: YES user_id=175228 There is nothing we should be able to do in Java code to cause a vm panic. 1.4 on linux so far has proven to be unstable for use with JBoss. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=376685&aid=567381&group_id=22866 _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
