JBoss Connectors Test
In a typical WildFly JBoss architecture, there are two main web connectors namely the Java I/O Connector and the AJP Connector. While the Java I/O connector uses the Java I/O to serve HTTP/HTTPS connections directly to the platform, the AJP Connector uses Apache’s Portable Runtime (APR) native code library. Often, the connectors of the WildFly JBoss server receive a large number of requests for processing. In such cases, it becomes inevitable to identify how many requests are processed by the connector, how long it takes to process a request etc. The JBoss Connectors test exactly helps you figure out your concerns! This test not only monitors the number of incoming requests processed by each connector but also evaluates the time taken for processing the requests and the maximum time taken to process a single request. This test also sheds light on the amount of data used in processing the requests and errors encountered while processing the requests.
Target of the test : A WildFly JBoss server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for each connector on the target WildFly JBoss that is to be monitored
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Request count: |
Indicates the number of incoming requests processed by this connector. |
Number |
A high value is desired for this measure. |
Processing time: |
Indicates the total time taken by this connector to process the incoming requests. |
Mins |
A low value is desired for this measure. The maxThreads parameter of the WildFly JBoss is set to 200 by default. This implies that the maxThreads parameter actually creates a thread pool behind the connector and processes the incoming requests. If no threads are available or the maximum limit for the number of threads is reached, processing of new requests is delayed which eventually leads to the piling up of requests. Also, a request may take too long to be processed if the request is malign or if adequate resources are not available for processing. |
Max time: |
Indicates the maximum time taken by this connector to process an incoming request. |
Mins |
An abnormally high value clearly indicates a performance issue or lack of threads that process the requests. |
Bytes sent: |
Indicates the number of bytes sent by this connector for processing the requests. |
Number |
Comparing the value of these measures across the connectors will help you identify the connector that is using the maximum bytes for processing the requests. |
Bytes received: |
Indicates the number of bytes received by this connector for processing the requests. |
Number |
|
Error count: |
Indicates the number of errors encountered by this connector while processing the requests. |
Number |
Ideally, the value of this measure should be zero. |