Bugs item #840496, was opened at 2003-11-11 20:15 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=840496&group_id=22866
Category: JBossWeb Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: David Ward (dward2) Assigned to: Scott M Stark (starksm) Summary: Cocoon war dir hot-redeploy causes JBoss Shutdown Initial Comment: I've discovered a problem that only happens with jboss 3.0 + tomcat + cocoon 2.0 + expanded war directory, relating to hot-redeploy. Basically, if you have a cocoon.war/ *directory* web application, and touch it's web.xml file, JBoss shuts down! Here are the steps to re-create: 1) Download a completely fresh jboss-3.0.7_tomcat-4.1.24 from sourceforge. 2) Download a completely fresh cocoon-2.0.4 (vm14) from apache. 3) Dropped cocoon.war in jboss' deploy directory. 4) Started up jboss. 5) Hit the cocoon servlet (got a sitemap error but didn't care) 6) "touch" cocoon.war. 7) NO REDEPLOY PROBLEM 8) Hit the cocoon servlet (got same sitemap error but still didn't care - at least could still hit it). 9) Stop jboss. 10) Delete the db, tmp and log dirs to be completely clean distro again. 11) Explode the cocoon.war file into cocoon.war/ *DIRECTORY INSTEAD*. 12) Start up jboss. 13) Hit the cocoon servlet (sitemap error; still don't care) 14) "touch" cocoon.war/WEB-INF/web.xml 15) *** REDEPLOY PROBLEM: jboss shuts down!!!!!! *** JBoss/Jetty does not do this. JBoss 3.2.x does not do this. A JBoss/Tomcat webapp without Cocoon does not do this. JBoss/Tomcat with a Cocoon war *file* does not do this. It has to be JBoss 3.0/Tomcat with a Cocoon 2.0 war *directory*, and you touch it's web.xml file to cause a redeploy. I have tested it on many different combinations, and here is the breakdown: 1) jboss-3.0.7_tomcat-4.1.24 + cocoon-2.0.4 - FAILED 2) jboss-3.0.8_tomcat-4.1.24 + cocoon-2.0.4 - FAILED 3) jboss-3.0.8_tomcat-4.1.27 + cocoon-2.0.4 - FAILED 4) jboss-3.0.8_tomcat-4.1.29 + cocoon-2.0.4 - FAILED 5) jboss-3.2.2 (tomcat_4.1.27) + cocoon-2.0.4 - PASSED 6) jboss-3.0.8_tomcat-4.1.24 + cocoon-2.1.2 - PASSED, though 500 errors Something was fixed in JBoss 3.2.2 / Tomcat that fixed this problem. Does anyone have any idea what this was? Unfortunately, we cannot upgrade to JBoss 3.2.2 right now. If the fix is known, can it be backported back to 3.0? A jboss-3.0.9_tomcat-4.1.29 with the backported fix would be awesome and greatly appreciated! BTW, with JBoss 3.2.2, it looks like the shutdown was intercepted; here's a line from the console: 22:43:58,980 INFO [STDOUT] Mon Nov 03 22:43:58 EST 2003 SHUTDOWN : System.exit() was not called When I see that line with 3.2.2, the redeploy finishes and JBoss does not shutdown. Maybe find where that log is done and see what can be similarly done in 3.0.x to intercept the shutdown? Last bit of info: This is using Sun JDK 1.4.1 and 1.4.2. It is recreateable on Windows; not sure about Linux and MacOSX. Thanks! David ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2003-11-12 16:13 Message: Logged In: YES user_id=175228 Put the server in a debugger and set a break point on the System.exit call and show the stack trace to see who is calling it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=840496&group_id=22866 ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
