Description of monitor

The maximum number of bean instances that can be stored in the pool while not in use at a given point in time.

Description of possible problems and their impact

If the PoolCurrentlyUsedObjects is greater then the MaxPoolSize, the monitor is not configured properly or the user load is too high.

Boundary conditions for the metric (thresholds)

We recommend you set the following:

GY 2,147,483,646 YR 2,147,483,647 RY 2,147,483,647 YG 2,147,483,646

Recommended procedure if a problem occurs

If the reason for the high usage is the large number of requests for bean instances, it means that there is a heavy load on the application and the maximum pool size should be increased in the deployment descriptor.

Description of monitor

The number of times all bean instances have been passivated, which is the number of times ejbPassivate() callback method was invoked on all bean instances.

Description of possible problems and their impact

A too large number can indicate a huge user load on the server. 

Boundary conditions for the metric (thresholds)

We recommend you set the following:

GY 2,147,483,646 YR 2,147,483,647 RY 2,147,483,647 YG 2,147,483,646

Description of monitor

The maximum number of bean instances that can be stored in the pool while not in use at a given point in time.

Description of possible problems and their impact

If the PoolCurrentlyUsedObjects is greater than the MaxPoolSize, the monitor is not configured properly or the user load is too high.

Boundary conditions for the metric (thresholds)

We recommend you set the following:

GY 2,147,483,646 YR 2,147,483,647 RY 2,147,483,647 YG 2,147,483,646

Recommended procedure if a problem occurs

If the reason for the high usage is the large number of requests for bean instances, it means that there is a heavy load on the application and the maximum pool size should be increased in the deployment descriptor.

Description of monitor

The maximum number of bean instances that can be stored in the pool while not in use at a given point in time.

Description of possible problems and their impact

If the PoolCurrentlyUsedObjects is greater than the MaxPoolSize, the monitor is not configured properly or the user load is too high.

Boundary conditions for the metric (thresholds)

We recommend you set the following:

GY 2,147,483,646 YR 2,147,483,647 RY 2,147,483,647 YG 2,147,483,646

Recommended procedure if a problem occurs

If the reason for the high usage is the large number of requests for bean instances, it means that there is a heavy load on the application and the maximum pool size should be increased in the deployment descriptor.

Description of monitor

The number of bean instances in the pool that are currently used by the application (the instances). They are stored within the pool but at the moment are outside of it processing a client request.

Description of possible problems and their impact

Pool usage is the ratio between PoolCurrentlyUsedObjects and MaxPoolSize. It is not a problem to have a high pool usage. However, if it is above 100%, this can prevent servicing further requests for a bean instance without creating new objects. As creating new objects is more expensive than reusing existing ones, this could deteriorate the performance and increase the memory consumption. At 100% usage rate, further requests are going to wait, if the pool is configured not to create excess objects.

High pool usage can also mean that many bean instances are used without being returned in the pool.

Boundary conditions for the metric (thresholds)

We recommend you set the following:

GY 2,147,483,646 YR 2,147,483,647 RY 2,147,483,647 YG 2,147,483,646

Recommended procedure if a problem occurs

If the reason for the high usage is the large number of requests for bean instance, this means that there is heavy load on the application and the maximum pool size should be increased in the deployment descriptor.