The minimal shutdown is very sensative to the implementation details of the server because there is no jmx invoker in this config. The shutdown relies on the behavior of a service undeployment calling System.exit so JBAS-3050 has likely changed how this behaves. I don't remember why this service could not use a jmx message instead.
> -----Original Message----- > From: Rajesh Rajasekaran > Sent: Wednesday, April 05, 2006 8:59 AM > To: Adrian Brock; QA > Cc: Alexey Loubyansky; Amit Bhayani; Anil Saldhana; Bela Ban; > Bill Burke; Brian Stansberry; Clebert Suconic; Dimitris > Andreadis; Emmanuel Bernard; [EMAIL PROTECTED]; > jboss-development@lists.sourceforge.net; > [EMAIL PROTECTED]; Kabir Khan; Ryan Campbell; Ruel Loehr; > Scott M Stark; Thomas Diesler; Tom Elrod > Subject: RE: jboss-4.0-testsuite Build Failed > > The "all" config fails to start because port 1098 is still in > use by the "minimal" configuration which started up earlier. > The minimal waits for 60 secs to completely shut down before > which the "all" config starts. I guess this change is related > to the following issue. > http://jira.jboss.com/jira/browse/JBAS-3050 > > This can be verfied by running the testsuite manually. "ant > tests" from the testsuite folder. > This can be avoided by allowing the testsuite to wait for 60 > secs or more before different configurations start up. > > Thanks > Rajesh ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
