Agileload Logo

Anomalies Management

The JBoss collector allows to insert the following types of anomalies in an anomalies profile: JBoss 4, 5, 6

JBoss 4

JVM Used Memory

JVM Used Memory Alert is the ratio between used memory and current memory in the JVM Heap.

The JVM Used Memory is the currently memory really used by the memory. The current memory in the heap is different, because it matches to the current memory that the JVM keeps, but don't use. If the used memory is too important, the JVM will then increase the size of the allocated memory.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

JVM Total Memory

JVM Total Memory Alert is the ratio between current allocated memory and maximum server memory.

The max memory is the limit that the JVM can allocate from the server. If the JVM needs many memory (which is equals to the used memory), then, it will need to allocate new memory, and if the allocated memory brings closer to the max memory, the server may raises the OutOfMemory exception, which will create a deny of services.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

Thread Pool Size

Thread Pool Size alert is raised when the ratio of used thread on total thread is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

Connector Error Count

Connector Error Count (per second).

A Connector Error occurs when a JBoss Connector was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 20
Severity 3: The ratio is greater than 50

Connector Thread Busy

Connector Thread Busy alert is raised when the ratio of busy thread on total thread is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

WebModule Rejected Session

A 'WebModule Rejected Session' occurs when all WebModule sessions slots are used. This limit is configurable in the WebModule parameters, but this parameter in unlimited by default. This anomaly will also help you to detect problem with sessions that are not deleted correctly.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 50
Severity 3: The ratio is greater than 100

Servlet Error Count

Servlet Error Count (per second).

A 'Servlet Error' occurs when a servlet was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 20
Severity 3: The thread count is greater than 50

JCA Connection Pool Used

'JCA Resource Pool Used' is the number of active connections divided by the capacity of the pool.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

JCA Waiting Thread

JCA Resource Waiting Threads is the number of threads waiting for a free instance of a connections.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 2
Severity 3: The thread count is greater than 6

JTA Rollback

JTA Rollback Alert is raised when the number of transactions rolled back divided by the total of transactions is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 25%
Severity 2: The ratio is greater than 50%
Severity 3: The ratio is greater than 60%

JBoss 5

JVM Used Memory

JVM Used Memory Alert is the ratio between used memory and current memory in the JVM Heap.

The JVM Used Memory is the currently memory really used by the memory. The current memory in the heap is different, because it matches to the current memory that the JVM keeps, but don't use. If the used memory is too important, the JVM will then increase the size of the allocated memory.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

JVM Total Memory

JVM Total Memory Alert is the ratio between current allocated memory and maximum server memory.

The max memory is the limit that the JVM can allocate from the server. If the JVM needs many memory (which is equals to the used memory), then, it will need to allocate new memory, and if the allocated memory brings closer to the max memory, the server may raises the OutOfMemory exception, which will create a deny of services.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

Connector Error Count

Connector Error Count (per second).

A Connector Error occurs when a JBoss Connector was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 20
Severity 3: The ratio is greater than 50

Connector Thread Busy

Connector Thread Busy alert is raised when the ratio of busy thread on total thread is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

WebModule Rejected Session

A 'WebModule Rejected Session' occurs when all WebModule sessions slots are used. This limit is configurable in the WebModule parameters, but this parameter in unlimited by default. This anomaly will also help you to detect problem with sessions that are not deleted correctly.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 50
Severity 3: The ratio is greater than 100

Servlet Error Count

Servlet Error Count (per second).

A 'Servlet Error' occurs when a servlet was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 20
Severity 3: The thread count is greater than 50

WebService Error Count

WebService Error Count (per second).

A 'WebService Error' occurs when a request failed.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 20
Severity 3: The thread count is greater than 50

JBoss 6

JVM Used Memory

JVM Used Memory Alert is the ratio between used memory and current memory in the JVM Heap.

The JVM Used Memory is the currently memory really used by the memory. The current memory in the heap is different, because it matches to the current memory that the JVM keeps, but don't use. If the used memory is too important, the JVM will then increase the size of the allocated memory.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

JVM Total Memory

JVM Total Memory Alert is the ratio between current allocated memory and maximum server memory.

The max memory is the limit that the JVM can allocate from the server. If the JVM needs many memory (which is equals to the used memory), then, it will need to allocate new memory, and if the allocated memory brings closer to the max memory, the server may raises the OutOfMemory exception, which will create a deny of services.

The default anomaly conditions are:
Severity 1: The ratio is greater than 75%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

Connector Error Count

Connector Error Count (per second).

A Connector Error occurs when a JBoss Connector was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 20
Severity 3: The ratio is greater than 50

Connector Thread Busy

Connector Thread Busy alert is raised when the ratio of busy thread on total thread is greater than the selected severities.

The default anomaly conditions are:
Severity 1: The ratio is greater than 70%
Severity 2: The ratio is greater than 80%
Severity 3: The ratio is greater than 90%

WebModule Rejected Session

A 'WebModule Rejected Session' occurs when all WebModule sessions slots are used. This limit is configurable in the WebModule parameters, but this parameter in unlimited by default. This anomaly will also help you to detect problem with sessions that are not deleted correctly.

The default anomaly conditions are:
Severity 1: The ratio is greater than 0
Severity 2: The ratio is greater than 50
Severity 3: The ratio is greater than 100

Servlet Error Count

Servlet Error Count (per second).

A 'Servlet Error' occurs when a servlet was unable to answer to a request.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 20
Severity 3: The thread count is greater than 50

WebService Error Count

WebService Error Count (per second).

A 'WebService Error' occurs when a request failed.

The default anomaly conditions are:
Severity 1: The thread count is greater than 0
Severity 2: The thread count is greater than 20
Severity 3: The thread count is greater than 50





Go back to the Learning center:



Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap