Closed glassfishrobot closed 11 years ago
@glassfishrobot Commented tmueller said:
How likely is it that a customer will see the bug and how serious is the bug? Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)? What CTS failures are caused by this bug?
This is a regression caused by a previous performance fix to the MonitoringBootstrap service.
How risky is the fix? How much work is the fix? Is the fix complicated?
Low cost, low risk. Just adding a null check in one place.
Is there an impact on documentation or message strings? No
Which tests should QA (re)run to verify the fix did not destabilize GlassFish? Tests that access the monitoring feature of the console.
Which is the targeted build of 4.0 for this fix? b85.
If this an integration of a new version of a component from another project, what are the changes that are being brought in? This might be list of Jira issues from that project or a list of revision messages. N/A
@glassfishrobot Commented tmueller said: Approved for 4.0.
@glassfishrobot Commented tmueller said: Fixed in revision 61421.
@glassfishrobot Commented Was assigned to tmueller
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-20306
@glassfishrobot Commented Reported by taman
@glassfishrobot Commented Marked as fixed on Sunday, April 14th 2013, 12:14:11 pm
Reproduce Scenario:
Check server.log and you will see the following errors:
Environment
Windows 7 SP1 x64 bit Mac OS X 10.8.3 Glassfish v4_b84
Affected Versions
[4.0_dev]