Tomcat Anomalies

The Tomcat collector allows to insert the following types of anomalies in an Anomalies profile:

JVM Used Memory

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

The JVM Used Memory is the currently memory really used by the JVM. The current allocated memory is different, because it matches the current memory that the JVM keeps, but not 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 Alert occurs when a Tomcat Connector was unable to answer to a specifical request made by a user.

This generally happens when the server has a big problem.

The default anomaly conditions are:

Severity 1: The error count is greater than 0
Severity 2: The error count is greater than 20
Severity 3: The error count is greater than 50

Connector Busy Threads

Connector Thread Busy Alert raises when the thread pool of a connector has a severity percentage of its threads that are busy.

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 Sessions

WebModule Rejected Sessions Alert raises when all WebModule sessions slots are used.

This limit is configurable in the WebModule parameters, but this parameter in unlimited by default. This alert will also help you to detect problem with sessions that are not deleted correctly.

The default anomaly conditions are:

Severity 1: The rejected sessions are greater than 0
Severity 2: The rejected sessions are greater than 50
Severity 3: The rejected sessions are greater than 100

Servlet Error Count

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

The default anomaly conditions are:

Severity 1: The error count is greater than 0
Severity 2: The error count is greater than 20
Severity 3: The error count is greater than 50


Servlet Response Time

Servlet response time is the ratio of recent average response time (last polling cycle) to the historical average response time (since the server was restarted).

The default anomaly conditions are:

Severity 1: The ratio is greater than 5%
Severity 2: The ratio is greater than 50%
Severity 3: The ratio is greater than 100%




Go back to the Learning center:


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