Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

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
Copiar enlace

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:
  1. Log in as the user with ownership permissions for the JBoss A-MQ installation.
  2. Open a command shell at InstallDir.
  3. Start the broker using the start command.
    Expand
    Windowsbin\start.bat
    Unix./bin/start
  4. Run the producer client with the following command:
    Linux/UNIX
    ./bin/client "activemq:producer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat "activemq:producer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    The producer will connect to the broker and produce 100 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: {}
$
    Copy to Clipboard Toggle word wrap
  5. To check that the messages have been enqueued, enter the following command:
    Linux/UNIX
    ./bin/client activemq:dstat
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat activemq:dstat
    Copy to Clipboard Toggle word wrap
  6. Run the consumer client with the following command:
    Linux/UNIX
    ./bin/client "activemq:consumer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat "activemq:consumer --user Username --password Password"
    Copy to Clipboard Toggle word wrap
    The consumer will connect to the broker and consume 100 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: {}
$
    Copy to Clipboard Toggle word wrap
  7. To check that the messages have been dequeued, enter the following command:
    Linux/UNIX
    ./bin/client activemq:dstat
    Copy to Clipboard Toggle word wrap
    Windows
    .\bin\client.bat activemq:dstat
    Copy to Clipboard Toggle word wrap
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat