Qpid Connections Test

A Connection represents an open communication channel between application and Broker. Each connection utilises a single TCP/IP connection between the process of the application and the process of the Broker. The act of establishing a connection is therefore a relatively expensive operation. Qpid connections have fail-over and heart-beating capabilities. Fail-over is the ability to automatically re-establish a failed connection, either to the same Broker, or the next Broker in the broker list. Heartbeats when enabled, the Client and Broker exchange a heartbeat during periods of inactivity. This allows both peers to discover if the TCP/IP connection becomes inoperable in a timely manner. Using this test, the administrators can monitor whether/not the TCP/IP connection between the broker and the application is stable.

Target of the test : Apache Qpid Java Broker

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each Connection to the target Apache Qpid Java Broker.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.

Host

The IP address of the target server that is being monitored.

Port

The port number through which the Apache Qpid Java Broker communicates. The default port is 8080.

Username

By default, the eG agent executes REST APIs on the target component to collect the required metrics. For the eG agent to execute the REST APIs, a user with monitoring privilege is required. Specify the name of such a user in this text box.

Password

Specify the password corresponding to the user mentioned in the Username text box here.

Confirm Password

Confirm the password by retyping it here.

SSL

By default, the SSL flag is set to No, indicating that the target Apache Qpid Java Broker is not SSL-enabled by default. To enable the test to connect to an SSL-enabled Apache Qpid Java Broker, set the SSL flag to Yes.

Timeout

Specify the duration (in seconds) within which the query executed by this test should time out in this text box.

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:

  • 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

State

Indicates the current state of this TCP/IP connection between the broker and the application.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value

Numeric Value
Stopped 0
Quiesced 50
Uninitialized 60
Unavailable 70
Errored 80
Deleted 90
Active 100

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current state of this TCP/IP connection between the broker and the application.

Use the detailed diagnosis of this measure to figure out the Name, Last Inbound Message Time, Last IO Time, Last Message Time, Last Outbound Message Time and Oldest Transaction Start Time details.

Data in

It indicates the total size of all the messages received by this connection.

MB

A very low value is desired for this measure.

Data out

It indicates the total size of all messages delivered by this connection.

MB

 

Local transaction begins

It indicates the total number of started transactions.

Counts

A very high value is desired for this measure.

Local transaction open

It indicates the current number of open transactions.

Counts

A very low value is desired for these measures.

Local transaction rollback

It indicates the total number of rolled-back transactions.

Counts

Messages in

It indicates the total number of messages delivered by this connection.

Messages

 

Messages out

It indicates the total number of messages received by this connection.

Messages

 

Session count

It indicates the current number of sessions belonging to this connection.

Counts

A high value indicates that this connection has too many sessions open for an abnormal period of time. By comparing the value of this measure across connections, you can quickly identify the connection which has the maximum number of such sessions.

Transacted messages in

It indicates the total number of messages delivered by this connection within a transaction.

Messages

A very high value is desired for these measures. A transactional message is an automated message that’s triggered by an action a given consumer takes. Generally these messages include necessary or high-priority info, such as a receipt, delivery details or updates, or order confirmations - and because they’re triggered by that individual's unique actions, they’re always sent on an individual basis, rather than to a big list of potential recipients.

Transacted messages out

It indicates the total number of messages received by this connection within a transaction.

Messages