Hybris Task Engine Pooling Queue Test

For efficient functioning of task execution, tasks are retrieved from task engine database and are stored in task buffer. The tasks which are due for execution are stored in pooling queue, queued to be picked by worker thread for execution. It is important to monitor the queue performance to ensure that tasks are queued up properly, and are available for processing as soon as worker thread is available.

This test monitors pooling queue for task queuing and helps adjust task engine properties to enable task execution without unnecessary delays.

Target of the test : A SAP Hybris system

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each tenant

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

Specify the port at which the specified host listens. By default, this is 9002.

JMX Remote Port

Specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the JMX remote port number of the SAP Hybris monitoring application. The default is 12002.

JNDI Name

The JNDIname is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.

JMX User and JMX Password

If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX.

Confirm Password

Confirm the password by retyping it here.

Provider

This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the Provider as value “default”.

Timeout

Specify the duration (in seconds) for which this test should wait for a response from the target Java application. If there is no response from the target beyond the configured duration, the test will timeout. By default, this is set to 1000 seconds if the Mode is JMX

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.
Measures made by the test
Measurement Description Measurement Unit Interpretation

Pooling Buffer entries

Indicates the total number of entries in pooling buffer during the last measurement period.

Number

 

Pooling queue entries

Indicates the total number of entries in pooling queue during the last measurement period.

Milliseconds

  

Pooling queue condition entries

Indicates the total number of entries in pooling queue condition entries during the last measurement period.

Milliseconds

  

Pooling time rate

Indicates the average time each task spends in the pooling queue before it is picked for execution, expressed in terms of number of tasks executed.

Number/min

 

Queue entries

Indicates the total number of entries in queue during the last measurement period.

Number