Well, I tried to run stop.jar and it failed because the Logging
classes aren't in the classpath. If I put them in the classpath, then it
gets a NullPointerException in the logging classes. If I remove the
logging, then it runs, but it still doesn't really do what I would expect.
That is, it issues the "stop" command to all the MBeans. But that
doesn't unload them or cause the server to exit. You still have to go and
hit Ctrl-C in the console window, which causes all the MBeans to print the
"destroying"/"destroyed" messages, and then exits.
As far as I can tell, the only time you're going to issue the
"stop" command using stop.jar is when you're not on the local machine, or
you ran the process in the background and don't have access to a console.
In that case, I think you really want the server to shut everything down
and exit. Is there any reason not to make stop.jar do that? *Can* we
make it exit the whole thing or are there dangling threads beyond our
control that will prevent the VM from stopping?
Aaron
