Bug 1007001 - Upgrade remoting-jmx to 1.1.1.Final
Summary: Upgrade remoting-jmx to 1.1.1.Final
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JMX
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: EAP 6.2.0
Assignee: Darran Lofthouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 999622 1009762
TreeView+ depends on / blocked
 
Reported: 2013-09-11 17:09 UTC by Kabir Khan
Modified: 2013-12-15 16:19 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:19:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker REMJMX-68 0 Major Resolved ClientConnection should propagate JMRuntimeException 2013-12-16 09:01:38 UTC
Red Hat Issue Tracker REMJMX-72 0 Major Resolved Release Remoting JMX 1.1.1.Final 2013-12-16 09:01:38 UTC

Description Kabir Khan 2013-09-11 17:09:52 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Darran Lofthouse 2013-09-11 17:12:19 UTC 
Although may go straight to Final
Comment 2 Rostislav Svoboda 2013-09-12 08:48:46 UTC 
Ack - related to JMX Rbac
Comment 3 JBoss JIRA Server 2013-09-12 11:37:16 UTC 
Darran Lofthouse <darran.lofthouse> updated the status of jira REMJMX-68 to Resolved
Comment 4 JBoss JIRA Server 2013-09-12 21:42:49 UTC 
Kabir Khan <kabir.khan> made a comment on jira REMJMX-68

Discussing with Brian we decided this should be its superclass instead.
Comment 5 JBoss JIRA Server 2013-09-12 21:44:47 UTC 
Kabir Khan <kabir.khan> made a comment on jira REMJMX-68

Discussing with Brian we decided that the client should propagate JMRuntimeException rather than RuntimeMBeanException. The reason is JMRuntimeException is the parent for a bunch of useful exceptions, and JMRuntimeException itself does not require a cause in the constructor.
Comment 6 JBoss JIRA Server 2013-09-13 09:19:15 UTC 
Darran Lofthouse <darran.lofthouse> updated the status of jira REMJMX-68 to Reopened
Comment 7 JBoss JIRA Server 2013-09-13 13:00:00 UTC 
Darran Lofthouse <darran.lofthouse> updated the status of jira REMJMX-68 to Resolved
Comment 8 JBoss JIRA Server 2013-09-18 19:44:43 UTC 
Darran Lofthouse <darran.lofthouse> updated the status of jira REMJMX-72 to Resolved
Comment 10 Ladislav Thon 2013-09-30 10:20:18 UTC 
Given that bug 1009762 is already verified, I think we can move this to the "verified" state too, even though the non-productized remoting-jmx 1.1.1 version has never made it to any EAP 6.2.0.ERx.
Note You need to log in before you can comment on or make changes to this bug.