Very interesting Mr Bond...
new Thread(new Runnable()
{
public void run()
{
System.exit(0);
}
}, "ExitOnShutdown").start();
Can't do that either, because this cannot load a class from the
undeployed classloader. :-)
2006-04-05 17:36:57,751 DEBUG [org.jboss.deployment.MainDeployer]
Undeployed
file:/home/ejort/jboss-4.0/build/output/jboss-4.0.4.GA/server/minimal/deploy/shutdown.sar
2006-04-05 17:36:57,753 ERROR [STDERR] java.lang.NoClassDefFoundError:
java/lang/System
2006-04-05 17:36:57,753 ERROR [STDERR] at
org.jboss.test.jmx.shutdown.ExitOnShutdown$1.run(ExitOnShutdown.java:52)
2006-04-05 17:36:57,754 ERROR [STDERR] at
java.lang.Thread.run(Thread.java:534)
On Wed, 2006-04-05 at 17:33 +0100, Adrian Brock wrote:
> The problem is that ExitOnShutDown.java
> invokes exit() from stopService()
> this means the new code thinks the deployment thread is busy,
> because exit() never returns.
>
> I'll make stopService() fork a thread.
>
> On Wed, 2006-04-05 at 11:21 -0500, Scott M Stark wrote:
> > 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];
> > > [email protected];
> > > [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
--
xxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss Inc.
xxxxxxxxxxxxxxxxxxxxxxxx
-------------------------------------------------------
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&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
