- GlassFish Monitoring (Sun Java System Application Server)
GlassFish Monitoring
GlassFish (Sun Java System Application Server) 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.
The design of the LiveCycle Data Services monitoring module, based on industry standards like all our modules,
obviates the installation of third-party software on the servers to be monitored. Furthermore, the
monitor is shipped preconfigured to simplify the retrieval of the relevant data from your GlassFish
or SJAS / SGES application server.
GlassFish / SJAS / SGES dedicated 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.