On rare occasions, your JVM will not respond to the "./stop" command. When this happens, you'll need to stop the JVM process using the UNIX "kill" command. To kill your JVM, you'll be telling the operating system to remove the process that controls your JVM. This processes runs a perl script that must be stopped.

To kill Resin:

Open a telnet or ssh session to your user account.

Find the process identifier (PID) of your JVM's controlling perl script by typing this command:

ps x | grep perl

You will see a line something like this in the output:

18707 ? SW 0:00 [perl]

The first number (18707, in this case) is your JVM's PID.

Kill the JVM by typing "kill -9" and then your JVM's PID. Using the example above, this command would look like:

kill -9 18707

To make sure your JVM is not running anymore, check to see that all your java threads are not running:

ps x | grep java

If this command displays no java processes, you have successfully killed your JVM and you can skip the "killall" step below. If you have not killed your JVM completely, you will see lines like this:

18774 ? S 0:00 [java]

Kill all your java threads individually. You can do this quickly with one command. This command will kill all java processes, including any other JVMs you have running at the time.

killall java

After this, issue this command to make sure your java processes have dissappeared:

ps x | grep java

If you still have java processes, please contact Servlets.Net Support at support@servlets.net.

Killing Resin will also stop your private JVM process.