JBoss MQ Queues Test

Clients that are in the point-to-point paradigm typically use queues. They expect that message sent to a queue will be received by only one other client once and only once. If multiple clients are receiving messages from a single queue, the messages will be load balanced across the receivers. Queue objects, by default, will be stored under the JNDI queue/ sub context.

This test auto-discovers the queues on the WildFly JBossserver, and monitors each queue for the size, number, and type of messages it holds, so that impending overloads and probable delivery bottlenecks can be proactively isolated and corrected.

Target of the test : A WildFly JBoss server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each queue of the target WildFly JBoss server that is to be monitored

Configurable parameters for the test
  1. TEST PERIOD - How often should the test be executed
  2. Host – The host for which the test is to be configured
  3. port– The port at which the specified HOST listens. By default, this is 9990.
  4. SSL – If the WildFly JBoss server being monitored is an SSL-enabled server, then set the sslflag to Yes. If not, then set the sslflag to No.
  5. IS JBOSS RUNNING IN DOMAIN MODE?– Specify whether the server to be monitored is currently running in DOMAIN MODE or not. By default, this flag is set to No which implies that the server is currently running in STANDALONE MODE. If you have started the target JBoss server using the default web profile configuration in domain mode i.e, if you have executed the ./domain.sh command from the <JBoss_INSTALL_DIR>/bin directory, then specify Yes against this flag.
  6. JBOSS HOST NAME – Specify whether the target server to be monitored is a master or a slave in a JBoss cluster. By default, none will be specified here which implies that the target JBoss server is a standalone server. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to know how to identify whether the target server is a master or slave in your environment.
  7. JBOSS SERVER INSTANCE NAME– Specify the name of the server instance that is to be monitored. By default, none will be specified here. Refer to Identifying the host name and server instance name of the WildFly JBoss server running in Domain mode to identify the name of the server instance that is to be monitored. 
  8. MANAGEMENT USER and MANAGEMENT PASSWORD– Specify the credentials of the user who is authorized to access the management console of the target JBoss server. To create a new user, refer to Creating a new management user in the WildFly JBoss server of this document.
  9. confirm password– Confirm the MANAGEMENT PASSWORD by retyping it here.
Measures made by the test:
Measurement Description Measurement Unit Interpretation

Max queue depth:

Indicates the max value of the number of messages that were in this queue since the start of the queue.

Number

 

Current queue depth:

Indicates the number of messages that are currently in this queue.

Number

A high value is indicative of server workload, or a delivery bottleneck.

Queue occupied:

Indicates the percentage of queue length that is occupied by messages.

Percent

A high value is a cause for concern as it could indicate a bottleneck in message delivery, which may be heavily populating the queue with messages.

Messages delivered:

Indicates the number of messages in this queue that have been delivered.

Number

A high value is desired for this measure.

Messages scheduled:

Indicates the number of messages in this queue that are currently scheduled to be delivered.

Number

 

Messages added:

Indicates the number of messages that were added to this queue during the last measurement period.

Number

 

Last message sent time:

Indicates the time that elapsed since the last message was sent from this queue.

Secs

Ideally, the value of this measure should be low. A high value is indicative of a delay in message delivery or a message processing bottleneck.

Subscriber count:

Indicates the number of subscribers registered with this queue.

Number

 

Receivers count:

Indicates the number of clients who are currently configured as receivers of messages from this queue.

Number

 

Message processing rate:

Indicates the rate at which messages are being processed by this queue.

Msgs/sec