This section lists the following known issues with SNMP monitoring:
You can retrieve j2eeJCATable and j2eeJcaConnPoolStatTable data only for the domain administration server (DAS). You cannot retrieve this information for other server instances.
This issue has two parts:
When a stand-alone web module is disabled, the value of the j2eeModSMState attribute in the j2eeModTable is still shown as running (4).
When a web module within an application is disabled, the j2eeModTable entry for the web module disappears altogether.
The workarounds are as follows:
Restart the clusters or server instances on which the stand-alone web module is deployed.
JDBC and connector connection pools do not appear in the j2eeRsrcTable when the corresponding monitoring levels are set to OFF.
Set monitoring to HIGH for JDBC and connector connection pools. See the Sun GlassFish Enterprise Manager SNMP Monitoring 1.0 Installation and Quick Start Guide.
The value of the statistics provider attribute for the main GlassFish MBean object is always set to false. Therefore, *StatProv attributes in various GlassFish SNMP data tables may be set to false even when statistics are available.
If an application is disabled and then undeployed, the application continues to appear in the j2eeAppTable for SNMP monitoring.
Restart the clusters or server instances on which the application was undeployed.
JDBC and connector connection pools are not removed from the J2eeRsrcTable after they have been deleted.
Restart the clusters or server instances from which the JDBC and connector connection pools were deleted.
When you delete a virtual server, the corresponding entry in the j2eeModTable does not get deleted.
Restart the clusters or server instances from which the virtual server was deleted.