2.6.5. Stop JBoss Enterprise Application Platform 6

Task Summary:

The way that you stop JBoss Enterprise Application Platform 6 depends on how it was started. This task covers stopping an instance that was started interactively, stopping an instance that was started by a service, and stopping an instance that was forked into the background by a script.

Note

This task does not address stopping a server or server group in a Managed Domain. For those scenarios, see Section 2.8.3, “Stop a Server Using the Management Console”.

Procedure 2.1. Task:

  1. Stop an instance which was started interactively from a command prompt.

    Press Ctrl-C in the terminal where JBoss Enterprise Application Platform 6 is running.

  2. Stop an instance which was started as an operating system service.

    Depending on your operating system, use one of the following procedures.

    • Red Hat Enterprise Linux

      For Red Hat Enterprise Linux, if you have written a service script, use its stop facility. This needs to be written into the script. Then you can use service scriptname stop, where scriptname is the name of your script.

    • Microsoft Windows Server

      In Microsoft Windows, use the net service command, or stop the service from the Services applet in the Control Panel.

  3. Stop an instance which is running in the background (Red Hat Enterprise Linux)

    1. Locate the instance from the process list. One option is to run the command ps aux |grep "[j]ava -server". This returns one result for each JBoss Enterprise Application Platform 6 instance that is running on the local machine.
    2. Send the process the TERM signal, by running kill process_ID, where process_ID is the number in the second field of the ps aux command above.
Result:

Each of these alternatives shuts JBoss Enterprise Application Platform 6 down cleanly so that data is not lost.