[jbosstools-issues] [JBoss JIRA] (JBIDE-12900) MBean explorer should be able to refresh (on demand?)

Martin Malina (JIRA) jira-events at lists.jboss.org
Thu Nov 15 10:11:21 EST 2012


     [ https://issues.jboss.org/browse/JBIDE-12900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Malina closed JBIDE-12900.
---------------------------------



I'm closing this JIRA as it is now possible to disconnect and connect again. But I created JBIDE-13082 asking if we could have something more visible to the user.
Verified in JBT 4.0.0.Beta2a B74.
                
> MBean explorer should be able to refresh (on demand?)
> -----------------------------------------------------
>
>                 Key: JBIDE-12900
>                 URL: https://issues.jboss.org/browse/JBIDE-12900
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: jmx
>    Affects Versions: 4.0.0.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>              Labels: respin-a
>             Fix For: 4.0.0.Beta2, 4.0.0.CR1
>
>
> When you execute an operation on an MBean that will remove said MBean (or any other MBean) this change is not reflected. And there is no way to refresh the mbeans. For example say you want to remove a deployment scanner. You run the remove operation on it. It works. But you can still see the mbean. And if you click on Attributes on that mbean and select an attribute you get an error:
> {code}
> Unavailable
> javax.management.InstanceNotFoundException: JBAS011340: No MBean found with name jboss.as:subsystem=deployment-scanner,scanner=jbosstoolsscanner1
> 	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.createInstanceNotFoundException(ModelControllerMBeanHelper.java:382)
> 	at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:179)
> 	at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getAttribute(ModelControllerMBeanServerPlugin.java:69)
> 	at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:154)
> 	at org.jboss.remotingjmx.protocol.v1.ServerProxy$GetAttributeHandler.handle(ServerProxy.java:773)
> 	at org.jboss.remotingjmx.protocol.v1.ServerProxy$MessageReciever$1.run(ServerProxy.java:215)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> 	at java.lang.Thread.run(Thread.java:679)
> {code}
> We need to find a way to address this. At the very least there should be a "refresh button" somewhere that would refresh the mbeans for a given jmx connection (or all). Even better would be if we could detect the removal of the mbean somehow.

--
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


More information about the jbosstools-issues mailing list