[GLASSFISH-16825] If It is Impossible to Transform Classes -- Disable Monitoring Created: 08/Jun/11  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: monitoring
Affects Version/s: 3.1
Fix Version/s: not determined

Type: Bug Priority: Major
Reporter: Byron Nevins Assignee: Byron Nevins
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-next, 3_1_1-scrubbed, 3_1_x-exclude


Very early in the process of booting up a GF Server we should check and see if it is possible to do bytecode transformation of classes. If NOT then we should :

1) if monitoring is enabled, log a SEVERE message about the problem and then disable monitoring – but just for that run. Don't persist it in domain.xml

2) if monitoring is disabled – then do nothing

In either case if the user runs "enable-monitoring" we should return a strongly worded error.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Mon May 25 23:30:44 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.