I guess there isn't such a concept as a process id like there is with apache and some other programs.
You could submit a bug or feature request on sourceforge so that shutdown can be smart to handle multiple instances of jboss. I'd stick with the cntl-c method if you have multiple instances of jboss on the same machine. If you don't have the process in the console (so you can't press cntl-c) you can always (with linux anyway) look up the main process and kill it. That will do the same thing as cntl-c but you'd have to note the process when you start jboss as to not get it confused with other jboss or java programs. -Dennis On Fri, 2002-05-03 at 04:29, Marius Kotsbak wrote: > On fre, 2002-05-03 at 00:18, Dennis Muhlestein wrote: > > If you run jboss on a remote machine, and you don't have it running > > in the forground and can't do a cntl-c, > > you can use the jboss_dir/bin/shutdown.sh (or bat) file as well. > But this script seems to kill all jboss instances running on the host, > including different versions..... > > > > > > > > > > > > > On Thu, 2002-05-02 at 15:58, Prabhakar Chaganti wrote: > > > Do a ctrl-c on the terminal/console. That should properly shutdown the server. > > > > > > prabhakar chaganti > > > > > > On Thursday 02 May 2002 05:17 pm, Kaveh wrote: > > > > What is the proper way of stopping the Server? > > > > > > > > > _______________________________________________________________ > > > > > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > > > the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > >
signature.asc
Description: This is a digitally signed message part
