GlassFish v3 Error Message Reference
\

MNTG

This page lists error messages with the MNTG prefix.

See How to Contribute for more information about adding to and enhancing the information on this page.

----MNTG0101 Discovering the ProbeProviders

Cause

TBD

Solution

TBD

----MNTG0102 Discovering the XML ProbeProviders from lib/monitor

Cause

TBD

Solution

TBD

----MNTG0103 Couldn''t find the module, when loading the monitoring providers from XML directory : {0}

Cause

TBD

Solution

TBD

----MNTG0104 Unable to load the ProbeProvider

Cause

TBD

Solution

TBD

----MNTG0105 Unable to load the ProbeProvider

Cause

TBD

Solution

TBD

----MNTG0106 Level change event received, {0} New Level = {1}, Old Level = {2}

Cause

TBD

Solution

TBD

----MNTG0107 Enabling the monitoring for all the stats with level = {0}

Cause

TBD

Solution

TBD

----MNTG0108 Disabling the monitoring for all the stats

Cause

TBD

Solution

TBD

----MNTG0109 mbean-enabled flag is turned on. Enabling all the MBeans

Cause

TBD

Solution

TBD

----MNTG0110 mbean-enabled flag is turned off. Disabling all the MBeans

Cause

TBD

Solution

TBD

----MNTG0111 dtrace-enabled flag is turned on/off. Enabling/Disabling DTrace

Cause

TBD

Solution

TBD

----MNTG0112 monitoring-enabled flag is turned on. Enabling all the Probes and Stats

Cause

TBD

Solution

TBD

----MNTG0113 monitoring-enabled flag is turned off. Disabling all the Stats

Cause

TBD

Solution

TBD

----MNTG0201 Flashlight listener registration failed for listener class : {0} , will retry later

Cause

TBD

Solution

TBD

----MNTG0202 Invalid statsProvider (very likely a duplicate request), cannot unregister : {0}

Cause

TBD

Solution

TBD

----MNTG0203 Cannot find node {0} for statsProvider {1}

Cause

TBD

Solution

TBD

----MNTG0204 {0} is not a ManagedObject and will not be registered with Gmbal to create an MBean

Cause

TBD

Solution

TBD

----MNTG0205 Gmbal registration failed

Cause

TBD

Solution

TBD

----MNTG0206 Gmbal unregistration failed

Cause

TBD

Solution

TBD

----MNTG0207 module-monitoring-level or container-monitoring config element for {0} does not exist

Cause

TBD

Solution

TBD

----MNTG0208 Error unregistering the stats provider : {0}

Cause

TBD

Solution

TBD

----MNTG0209 Error resetting the stats provider : {0}

Cause

TBD

Solution

TBD

----MNTG0301 Cannot process XML ProbeProvider, xml = {0}

Cause

TBD

Solution

TBD

----MNTG0302 Cannot resolve the paramTypes, unable to create this probe - {0}

Cause

TBD

Solution

TBD

----MNTG0303 Cannot resolve the paramTypes of the probe - {0}, Try giving a fully qualified name for the type

Cause

TBD

Solution

TBD

----MNTG0304 Can not match the Probe method ({0}) with any method in the DTrace object.

Cause

TBD

Solution

TBD

----MNTG0305 Invalid parameters for ProbeProvider, ignoring {0}

Cause

TBD

Solution

TBD

----MNTG0501 invalid pid, start btrace-agent using asadmin enable-monitoring with --pid option, you may get pid using jps command

Cause

TBD

Solution

TBD

----MNTG0502 btrace-agent.jar does not exist under {0}

Cause

TBD

Solution

TBD

----MNTG0503 btrace-agent.jar directory {0} does not exist

Cause

TBD

Solution

TBD

----MNTG0504 Encountered exception during agent attach

Cause

TBD

Solution

TBD

----MNTG0601 No providers identified from the xml

Cause

TBD

Solution

TBD