Hi,
you could also use the >server>:8082 agent and use the domain shutdown to
kill the server.
Regards,
Burkhard
- Original Message -
From: "Kaveh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 4:17 PM
Subject: [JBoss-user] stopping jboss 3.0
> What is the prop
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 j
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
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.
On Thu, 2002-05-02 at 15:58, Prabhakar Chaganti wrote:
> Do a ctrl-c on the terminal/console. That should properly shutdo
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
