Chapter 4. Verifying the Installation
Abstract
Once the installer has completed running it is a good idea to run a simple test to ensure that Red Hat JBoss A-MQ was properly installed.
4.1. Verify the Installation
JBoss A-MQ ships with a simple client utility that can be used to verify that the software was successfully installed. You use it to create a message producer and a message consumer that connect to the broker. If they run successfully, and you see—by checking the Fuse Management Console—that the broker processed the messages, then you can be confident that JBoss A-MQ was installed successfully.
To verify that JBoss A-MQ is properly installed:
- Log in as the user with ownership permissions for the JBoss A-MQ installation.
- Open a command shell at
InstallDir. - Start the broker using the start command.
Windows bin\start.bat Unix ./bin/start - Run the producer client with the following command:
- Linux/UNIX
./bin/client "activemq:producer --user Username --password Password"
- Windows
.\bin\client.bat "activemq:producer --user Username --password Password"
The producer will connect to the broker and produce 1000 messages. Example 4.1, “Test Producer Output” shows the producer's output.Example 4.1. Test Producer Output
$ ./bin/client "activemq:producer --user Username --password Password" client: JAVA_HOME not set; results may vary Logging in as admin 1073 [sshd-SshClient[6575deb1]-nio2-thread-3] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at [/0.0.0.0:8101, DSA, af:77:de:7f:c9:32:f0:b0:ed:12:0e:cd:56:35:fe:78] presented unverified {} key: {} $NoteThe producer command will only send messages to a broker with default port configuration. So, if you set up more than one JBoss A-MQ instance on the same machine, the producer will only send messages to the instance that uses the default ports. - To check that the messages have been enqueued, enter the following command:
- Linux/UNIX
./bin/client activemq:dstat
- Windows
.\bin\client.bat activemq:dstat
- Run the consumer client with the following command:
- Linux/UNIX
./bin/client "activemq:consumer --user Username --password Password"
- Windows
.\bin\client.bat "activemq:consumer --user Username --password Password"
The consumer will connect to the broker and consume 1000 messages. Example 4.2, “Test Consumer Output” shows the consumer's output.Example 4.2. Test Consumer Output
$ ./bin/client "activemq:consumer --user Username --password Password" client: JAVA_HOME not set; results may vary Logging in as admin 235 [sshd-SshClient[1d6f6a81]-nio2-thread-1] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier - Server at [/0.0.0.0:8101, DSA, af:77:de:7f:c9:32:f0:b0:ed:12:0e:cd:56:35:fe:78] presented unverified {} key: {} $ - To check that the messages have been dequeued, enter the following command:
- Linux/UNIX
./bin/client activemq:dstat
- Windows
.\bin\client.bat activemq:dstat
