Hi!
Aaron Mulder wrote:
> 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.
The dependency on the logging should have been removed a long time ago
(Marc added it, I noted the problem, but it wasn't changed back).
> 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.
This is because "stop" is "stop" (i.e. you can start/stop/start/stop the
server any nr of times you want) and not "quit". Please add "quit" (or
similar) if you want to.
> 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?
As above, because of the semantics of the word "stop". Please simply
make a new command with proper semantics.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
