AMH Threadpools Test

Alliance Messaging Hub (AMH) is a modular, financial messaging solution for corporate networks. It allows extensive throughput and sophisticated data management through the use of latest technology to manage messages and files. To optimize the performance of the system, AMH makes extensive use of multithreading through the threadpool available to the application. The AMH services pick the messages from the queues and process them in parallel threads. That's the reason the processing capacity of the system depends partly on threadpool capacity and how efficiently the threadpool is managing the processing the threads.

This test monitors the threadpool and collects the statistics around number of messages available in queues, number of threads running etc. These metrics provide the administrators with great insights about the queue processing and any inefficiencies can be spotted.

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 threadpool in Swift AMH node being monitored.

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 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.

Measures made by the test

Measurement	Description	Measurement Unit	Interpretation
High queue size	Indicates the highest number of messages in the queue to be picked for processing for the current node.	Number	High queue size means large number of messages in the queue, it will require busier threadpool as it will have to generate more threads for processing.
Low queue size	Indicates the lowest number of messages in the queue to be picked for processing for the current node.	Number	In case the queue size is low, it could be because of faster consumption by large number of threads.
Normal queue size	Indicates the average number of messages in the queue to be picked for processing for the current node.	Number	Both queue size and thread count should be optimal for efficient operation of the system.
High thread	Indicates the highest number of threads spawned to process the messages at any given time for the current node.	Number	High thread count might indicate longer processing time as the threads are not getting freed.
Low thread	Indicates the lowest number of threads spawned to process the messages at any given time for the current node.	Number