JBoss.orgCommunity Documentation

Chapter 6. Starting The Server

6.1. Standalone HornetQ
6.2. HornetQ In JBoss AS 5.x
6.3. HornetQ In JBoss AS 4.x
6.4. HornetQ In JBoss AS 6.0

To run a stand-alone server, open up a shell or command prompt and navigate into the bin directory. Then execute ./run.sh (or run.bat on Windows) and you should see the following output

         bin$ ./run.sh
         15:05:54,108 INFO  @main [HornetQBootstrapServer] Starting HornetQ server
         15:06:02,566 INFO  @main [HornetQServerImpl] HornetQ Server version 
         2.0.0.CR3 (yellowjacket, 111) started

HornetQ is now running.

Both the run and the stop scripts use the config under config/stand-alone/non-clustered by default. The configuration can be changed by running ./run.sh ../config/stand-alone/clustered or another config of your choosing. This is the same for the stop script and the windows bat files.

To run HornetQ in JBoss AS 5, you need to create the AS 5 profiles for HornetQ first. Then run JBoss AS 5 with one these profiles. For example, to run JBoss AS 5 with a non-clustered HornetQ server, got to $JBOSS_HOME/bin directory and type:

        bin$ ./run.sh -c default-with-hornetq
        15:18:35,460 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
        15:18:35,462 INFO  [ServerImpl] Release ID: JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=
        JBoss_5_1_0_GA date=200905221053)
        15:19:30,305 INFO  [HornetQServerImpl] HornetQ Server version 
        2.0.0.CR3 (yellowjacket, 111) started
        15:19:43,601 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=
        JBoss_5_1_0_GA date=200905221053)]Started in 1m:14s:556ms

To run HornetQ in JBoss AS 4 you must follow the same steps described for AS5 without forgetting to create the AS 4 profiles for HornetQ first.

From JBoss AS 6.0 M3 onwards, HornetQ is the default (built-in) JMS provider in JBoss AS, so there's no need to install it - it's already there.