JEUS Queues Test
A JMS queue represents the point-to-point (PTP) messaging model, which enables one application to send a message to another. PTP messaging applications send and receive messages using named queues. A queue sender (producer) sends a message to a specific queue. A queue receiver (consumer) receives messages from a specific queue.
This test auto-discovers the queues on a JEUS server, and reports the status of production and consumption on each queue. This test also reveals the number of messages that were processed/dispatched/delivered/expired/moved out of each queue. Besides, the count of consumers accessing each queue and the number of messages that are pending on each queue are also reported. By analyzing these details, administrator can proactively isolate and correct impending overloads and probable delivery bottlenecks on the queues.
Target of the test : A JEUS Web Application server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each queue on the target server.
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 at which the specified host listens. By default, this is 9736. |
Username and Password |
To enable the eG agent to communicate and continuously monitor the target JEUS server, the eG agent should be configured with the credentials of the admin user on the server. In highly-secure environments, administrators may not want to expose the credentials of the user possessing administrator privileges. In such environments, for monitoring the JEUS application server, administrators have an option to create a new user on the JEUS server and assign administrator privilege to that user. The steps to create a new user with administrator privilege are explained in Creating a User with Administrator Privileges |
Confirm Password |
Confirm the Password by retyping it here. |
Listener Port |
To collect metrics from the target server, the eG agent should be configured to use JMX to connect to the JRE used by the target server and pull out the performance metrics. By default, JMX support is enabled for the JRE used by the target server. The JMX connector listens on port 9736, by default. Therefore, type 9736 as the Listener Port. However, if the host is configured with multiple sever instances, then you should specify the port number at which the JMX listens in your environment. Ensure that you specify the same port that you configured while creating the listener (if required) using the JEUS WebAdmin Console. To know the details on the listener port, refer to Enabling JMX Support for the JEUS Web Application Server |
Export name |
The export name is the reference name of the RMI connector that is to be used as a JMX connector. The procedure to obtain the export name is detailed inEnabling JMX Support for the JEUS Web Application Server |
Server name |
Provide the name of the sever instance that is being monitored in the Server Name text box. Also, ensure that the JVM monitoring is enabled for the target server. To obtain the name of the server instance, refer to Enabling JMX Support for the JEUS Web Application Server |
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise 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:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||
---|---|---|---|---|---|---|---|---|---|
Production suspended |
Indicates whether/not the production has been suspended on this queue. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports whether the production is suspended in each queue. The graph of this measure however, is represented using the numeric equivalents only - 0 or 1. The detailed diagnosis of this measure lists the export name, type and dead letter destination of the queue. |
||||||
Consumption suspended |
Indicates whether/not the consumption has been suspended on this queue. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports whether the consumption is suspended in each queue. The graph of this measure however, is represented using the numeric equivalents only - 0 or 1. |
||||||
Consumers |
Indicates the current number of consumers accessing this queue. |
Number |
Compare the value of this measure across the queues to find out the queue that is excessively accessed by consumers. |
||||||
Processed messages |
Indicates the number of messages that were processed in this queue during the last measurement period. |
Number |
|
||||||
Processed messages rate |
Indicates the rate at which the messages were processed in this queue during the last measurement period. |
Messages/sec |
|
||||||
Pending messages |
Indicates the number of messages in this queue that are pending. |
Number |
A low value is desired for this measure. A consistent/significant increase in the value of this measure is a cause for concern. |
||||||
Dispatched messages |
Indicates the number of messages that were dispatched from this queue during the last measurement period. |
Number |
|
||||||
Dispatched messages rate |
Indicates the rate at which the messages were dispatched from this queue during the last measurement period. |
Messages/sec |
|
||||||
Delivered messages |
Indicates the number of messages that were delivered from this queue during the last measurement period. |
Number |
A high value is desired for this measure. A gradual/sudden drop in the value of this measure indicates a processing bottle-neck on the queue. |
||||||
Delivered messages rate |
Indicates the rate at which the messages were delivered from this queue during the last measurement period. |
Messages/sec |
|
||||||
Expired messages |
Indicates the number of messages that expired during the last measurement period. |
Number |
|
||||||
Expired messages rate |
Indicates the rate at which the messages expired during the last measurement period. |
Messages/sec |
|
||||||
Moved messages |
Indicates the number of messages that were moved out of this queue during the last measurement period. |
Number |
|
||||||
Moved messages rate |
Indicates the rate at which the messages were moved out of this queue during the last measurement period. |
Messages/sec |
|