Jboss MQ Queues Test

This test monitors the queues on the JBoss server. 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.

Target of the test : A JBoss application server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every queue on the JBoss application server.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

The port number at which the specified host listens to.

Measurement Mode

This test can extract metrics from JBoss using either of the following mechanisms:

  • By deploying the EgJBossAgent.sar and egjboss.war files on the target JBoss server;
  • By contacting the Java runtime (JRE) of JBoss viaJMX

To configure the test to usethe EgJBossAgent.sar and egjboss.war files, first, select the War File option. Then, refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter to know how to deploy these files on the target JBoss server.

On the other hand, if you want the test to use JMX instead, then first, select the jmx option. Then, follow the procedure detailed in the How to Monitor JBoss Application Server Using eG Enterprise? chapter to configure the test to use jmx. By default, the jmx option is chosen here.

JNDIName

This parameter appears only if the Measurement Mode is set to jmx. The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.

JMX Remote Port

This parameter appears only if the Measurement Mode is set to jmx. Here, specify the port at which the jmx listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file of the target JBoss server (refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter for more details).

JMX User, JMX Password, and Confirm Password

These parameters appear only if the Measurement Mode is set to jmx. If JMX requires authentication only (but no security), then ensure that the JMX User and JMX Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to the How to Monitor JBoss Application Server Using eG Enterprise? chapter. Confirm the password by retyping it in the Confirm Password text box.

SSL

This parameter appears only if the Measurement Mode is set to War File. Indicate Yes if the JBoss server is SSL-enabled.

URL

This parameter appears only if the Measurement Mode is set to War File. Specify the URL to be accessed to collect metrics pertaining to the JBoss server. By default, this test connects to a managed JBoss server and attempts to obtain the metrics of interest by accessing the local Mbeans of the server. Accordingly, by default, this parameter is set to http://<JBossServerIP>:<JbossServerPort>.

JMX Provider

This parameter appears only if the Measurement Mode is set to jmx. This test uses a JMX Provider to access the MBean attributes of the JBoss server and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from the JBoss server. If there is no response from the server beyond the configured duration, the test will timeout. By default, this is set to 240 seconds.

DD Frequency

Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements 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

 

Message processing rate

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

Msgs/Sec

 

Receivers count

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

Msgs/Sec

 

Current queue depth

Indicates the number of messages currently in this queue.

Number

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

Use the detailed diagnosis of this measure to know the JMS ID, Priority, Time, ProducerID, and the contents of each Message in the queue.

Scheduled messages count

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

Number

Use the detailed diagnosis of this measure to know the JMS ID, Priority, Time, ProducerID, and the contents of each Message that is scheduled for delivery.

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.

Message delivered

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

Number

A high value is desired for this measure.

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 who are registered with this queue.

Number

Use the detailed diagnosis of this measure to view the ID of all the subscribers registered with the queue.

Receivers count

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

Number

Use the detailed diagnosis of this measure to view the ID of all the receivers configured for this queue.