Bug #47562 | "NS" (No Severity Set) support issue severity unhandled by MEM | ||
---|---|---|---|
Submitted: | 23 Sep 2009 18:12 | Modified: | 19 Nov 2009 11:18 |
Reporter: | Josh Sled | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S3 (Non-critical) |
Version: | 2.1.0.1096 | OS: | Any |
Assigned to: | Josh Sled | CPU Architecture: | Any |
[23 Sep 2009 18:12]
Josh Sled
[1 Oct 2009 15:18]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified as reported in build 2.1.0.1096.
[9 Oct 2009 15:33]
Enterprise Tools JIRA Robot
Josh Sled writes: revno: 7486 committer: Josh Sled <jsled@asynchronous.org> branch nick: 2.1-bugs timestamp: Fri 2009-10-09 11:12:08 -0400 message: EM-3611, Bug#47562: handle "N[o Severity ]S[et]" support issue severity code.
[9 Oct 2009 16:24]
Enterprise Tools JIRA Robot
Josh Sled writes: and on trunk: revno: 7530 [merge] revision-id: jsled@asynchronous.org-20091009153723-809pghf6rul1fxcw parent: bill.weber@sun.com-20091008212330-ohb6dm092b6c5nsu parent: jsled@asynchronous.org-20091009151208-fv2ll0qaocrbaybc committer: Josh Sled <jsled@asynchronous.org> branch nick: local timestamp: Fri 2009-10-09 11:37:23 -0400 message: merge sync with branches/2.1/ ------------------------------------------------------------ revno: 7431.3.39 revision-id: jsled@asynchronous.org-20091009151208-fv2ll0qaocrbaybc parent: jsled@asynchronous.org-20091009150143-9baqtmemat9cq1zh committer: Josh Sled <jsled@asynchronous.org> branch nick: 2.1-bugs timestamp: Fri 2009-10-09 11:12:08 -0400 message: EM-3611, Bug#47562: handle "N[o Severity ]S[et]" support issue severity code.
[13 Oct 2009 21:07]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.2.0.1507.
[17 Nov 2009 19:53]
Enterprise Tools JIRA Robot
Keith Russell writes: Patch installed in versions => 2.1.1.1108.
[18 Nov 2009 5:52]
Enterprise Tools JIRA Robot
Marcos Palacios writes: Verified fixed in Monitor build 2.1.1.1108.
[19 Nov 2009 11:18]
Tony Bedford
An entry has been added to the 2.1.1 and 2.2.0 changelogs: Support issues can have a Severity from S1 through S4, but can also have a value of “NS” meaning “No Severity Set”. MySQL Enterprise Monitor was not able to parse this, which resulted in errors such as the following: 2009-09-23 13:53:51,812 ERROR [em-worker-pool-thread-6:monitor.support.DevSpPoller] error consuming successful response java.lang.IllegalArgumentException: No enum const class com.mysql.etools.monitor.support.SpIssue$Severity.NS at java.lang.Enum.valueOf(Enum.java:196) ...