Jboss MQ Topics Test

The JbossMQTopics test monitors the topics on the JBoss server. Topics are used in the publish-subscribe paradigm. When a client publishes a message to a topic, he expects that a copy of the message will be delivered to each client that has subscribed to the topic. However, if the client is not up, running and receiving messages from the topics, it will miss messages published to the topic. To get around this problem of missing messages, clients can start a durable subscription. This is like having a VCR record a show you cannot watch at its scheduled time so that you can see what you missed when you turn your TV back on. Similarly, messages meant for a durable subscriber are stored in the persistent cache even when the subscriber is inactive. These messages are delivered to durable subscribers when they connect to the server.

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 topic 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.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Max topic depth

Indicates the max value of the number of messages in the topic since the start of the queue.

Number

 

Msg process rate

Indicates the rate at which messages were being processed by the topic in the last measurement period.

Msgs/Sec

 

Durable messages count

Indicates the number of durable messages currently in the topic.

Number

 

Non-durable messages count

Indicates the number of non-durable messages currently in the topic.

Number

 

Total subjects count

Indicates the total number of subscribers to a topic.

Number

 

Durable subjects count

Indicates the number of durable subscribers to the topic.

Number

If the total number of durable subscribers is high, then we can expect the total durable messages to be stored on the server also to be relatively on the higher side.

Non-durable subjects count

Indicates the number of subscribers to the topic who are currently non-durable.

Number