Home / NeoLoad / Monitoring / App. Servers / GlassFish

GlassFish Monitoring

NeoLoad GlassFish monitoring module allows you to monitor remotely GlassFish or Sun Java System Application Server during load tests, resulting in a speedier diagnosis of performance slowdowns.

Features

Preconfigured Monitoring: Each module ships pre-configured with the performance counters tailored to your system.
Threshold Alerts: NeoLoad provides threshold values –derived from industry best practices- to raise the appropriate alerts.
Agentless Monitoring: The design of our monitoring modules, based on industry standards, ensures non-intrusive remote monitoring.
Real Time: The counter values and the threshold alerts are available as soon as the test is run.

Note: All the modules are included with the demo license.

Performance Counters

With GlassFish monitor, NeoLoad listens all of your GlassFish (since 2.0.x) or Sun Java System Application Server criticial counters, including:

Sessions. Data counters for this category contain usage information for HTTP sessions. Examples include the total number of accessed sessions and the average number of concurrently active HTTP sessions.
Cache. This section allows the user to monitor the cache for each application.
RequestProcessor. Provides management information on the processed requests.
EJB. This section allows the user to monitor all instances, transactions and cache counters for each EAR deployed on this server, and for each EJB contained therein.
JDBC Connection Pool. This section allows the user to monitor the JDBC connection pool counters. The counters are available for each server or connection pool.
JMS. This section allows the user to monitor the JMS runtime counters for each server instance.
Transaction Service. Monitors transactions for the whole server including committed et rolled-back ones.
Thread Pools. Monitors thread pool information for the WebLogic Server.
JVM. This section allows the user to collect information for each server on the Java Virtual Machine including counters related to the garbage collector. The Java Virtual Machine has a heap that is the runtime data area from which memory for all class instances and arrays are allocated. It is created at the Java Virtual Machine start-up. Heap memory for objects is reclaimed by an automatic memory management system which is known as a garbage collector. The heap may be of a fixed size or may be expanded and shrunk.
Description. Information on the application server configuration.