[jboss-jira] [JBoss JIRA] (WFLY-3073) MBeanServer.createMBean methods that take a classloader don't work

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12954104#comment-12954104 ] 

RH Bugzilla Integration commented on WFLY-3073:
-----------------------------------------------

Jan Martiska <jmartisk at redhat.com> changed the Status of [bug 1073106|https://bugzilla.redhat.com/show_bug.cgi?id=1073106] from ON_QA to VERIFIED
                
> MBeanServer.createMBean methods that take a classloader don't work
> ------------------------------------------------------------------
>
>                 Key: WFLY-3073
>                 URL: https://issues.jboss.org/browse/WFLY-3073
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMX
>    Affects Versions: 8.0.0.Final
>            Reporter: Stuart Douglas
>            Assignee: Kabir Khan
>             Fix For: 8.0.1.Final
>
>
> The MBeanServer.createMBean methods that take an "ObjectName loaderName" argument are completely broken in EAP 6.
> These methods call findDelegate to make sure there is already an existing MBean registered with the given name passed in for the new MBean, or else it throws an exception.
> This is obviously wrong, as there'd be no point in calling createMBean if it already existed.
> javax.management.InstanceNotFoundException: test:service=Test
> at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:1083)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.createMBean(PluggableMBeanServerImpl.java:253)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira