AMH JMS Connections Test
AMH uses JMS for connectivity with both inbound and outbound systems, so at any given time, there are a number of JMS connections established. These connections are vital for the message transmission between systems and ensure robust delivery and processing of swift messages. That's the reason it is important to monitor the connections so that administrators come to know of any issue of connection break as early as possible and take preventive action in timely manner.
This test monitors the JMS connections and reports various metrics like total connection, active connections etc. These metrics help administrator understand if connections are all functioning properly or if any investigation is required.
Target of the test : A Swift AMH node instance
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each Solace topic on which JMS connections are established.
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. |
SSL |
If the JBoss AS/EAP server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No. |
JMX Remote Port |
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 in the <JAVA_HOME>\jre\lib\management folder used by the target application Java Applications chapter. |
JNDI Name |
Specify the lookup name for connecting to the JMX connector of the Swift AMH. |
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. |
Measurement |
Description |
Measurement Unit |
Interpretation |
---|---|---|---|
Total Connections |
Indicates the total number of JMS connections currently existing. |
Number |
A very large number of connections might not be a good indicator of use, this measure should be used along with other measures to see if connections are used effectively. |
Active Connections |
Indicating the total number of active JMS connections. |
Number |
High percentage of active connections out of total connections is a good sign. |
Inactive connections |
Indicating the total number of inactive JMS connections. |
Number |
A high number of inactive connection means there is a lot of scope of connections recycling. |
Total timeout connections |
Indicating the total number of JMS connection which have been timed out. |
Number |
Connections which have been timed out needs to be investigated. |
Sessions per connection |
Indicates the average number of sessions running on each connection. |
Number |
If there are too many sessions hosted on a single connection, it might cause bandwidth issue and can cause delayed delivery of messages. Administrators may need to open new connections and transfer some of the sessions on new connections for optimal use of resources. |