Skip to end of metadata
Go to start of metadata


Requirements (historical, not current)
One Pager
Dependencies Analysis
v3 Support Readiness Presentation (internal)
v3 Sustaining TOI (internal)
Monitoring Statistics Usage (internal)
GF v3 Probes Dashboard (internal)
Making a Module Monitorable in v3


Oracle GlassFish Server 3.1 Administration Guide Monitoring, Chapter 8 Administering the Monitoring Service
Writing and Running JavaScript Clients to Monitor GlassFish Server
Oracle GlassFish 3.1 Add-on Component Development Guide, Chapter 5 Adding Monitoring Capabilities
Sun GlassFish Enterprise Manager DTrace Monitoring 3.0 Beta Installation and Quick Start Guide
Java EE 6 Webinar - Monitoring


Mort Learns How to Use
Monitoring Scripting of Clusters
Mort Learns Monitoring and Admin
How to Create a Pluggable Container
RESTful GlassFish Monitoring

Source Code Information

Management API - Public APIs and annotations - external to glassfish

Monitoring API - public APIs

Monitoring Infrastructure

  • v3/admin/monitor/src/main/java/org/glassfish/admin/monitor
    • - Discovers probe providers. Listens/handles monitoring configuration.
    • - Creates monitoring tree. Registers StatsProviders with Flashlight, GMBAL.
  • Tree Node API/Implementation
    • v3/admin/monitor/src/main/java/org/glassfish/flashlight/
    • v3/common/internal-api/src/main/java/org/glassfish/flashlight/
  • Reporter for asadmin get -m command
    • v3/core/kernel/src/main/java/com/sun/enterprise/v3/admin/
  • Flashlight Framework
    • v3/flashlight - Register probes with btrace
  • AMX** AMX loads MBeans (all MBeans or none) lazily in response to:
      • an MEJB connection
      • JMXConnector client connection
      • explicit call to bootAMX()
      • AmxPref.getAutoLoad() is true
v3 Design Information

Block Diagram
Block Diagram 2
GF Monitoring - ASArch Presentation
Monitoring Presentation for v3
v3 Express Monitoring


JIRA Sub-component name - monitoring
All unresolved monitoring bugs
All unresolved features/improvments
Bugs fixed in 3.1
Bugs that need devtests

  • You can step through with the Netbeans debugger in the monitoring code, except in the flashlight area and on a probe. The JVM will crash.
  • Set monitoring logging level to FINE in
  • Add jvm option to server-config domain.xml to turn on BTrace debugging
    <jvm-options>-javaagent:<gf install>/glassfish/target/glassfish3/glassfish/lib/monitor/btrace-agent.jar=dumpClasses=true,dumpDir=c:\tmp\dump2,debug=true,unsafe=true,noServer=true</jvm-options>
  • GMBAL debugging - In v3/admin/monitor/src/main/java/org/glassfish/admin/monitor/ at line 722, you can change debug to true
    • mom.setJMXRegistrationDebug(false);

Admin Devtests
{{cd appserv-tests/devtests/admin/cli
ant -Dteststorun=monitoring clean all}}
Module-specific Devtests

v3 Links



How Monitoring is Implemented in S1AS8.0 PE

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.

The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.