Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: ECLIPSE-590
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Lars Heinemann
Reporter: Claus Ibsen
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Fuse IDE

Cannot connect to MQ broker container from fabric explorer

Created: 16/Mar/12 02:03 PM   Updated: 28/Mar/12 05:44 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 2.1.0

File Attachments: None
Image Attachments:

1. broker-jmx.png
(150 kB)
Environment: 2.1.351
Issue Links:
Linked
 


 Description  « Hide
I created a fabric on my local machine.

I then created some child containers, such as a mq profile.

From Fuse IDE I can connect to the various containers, and use the terminal, and so forth.

However the JMX view of the broker container does not work.
I can do the JMX view on a Camel example profile, and that works fine.

I get a class not found exception for the broker.

java.lang.NoClassDefFoundError: org/apache/activemq/broker/jmx/QueueViewMBean
	at com.fusesource.ide.fabric.activemq.navigator.ActiveMQNodeProvider$1.run(ActiveMQNodeProvider.java:54)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper$1.doWithJmxConnector(FabricConnectionWrapper.java:162)
	at org.fusesource.fabric.service.JmxTemplate.execute(JmxTemplate.java:47)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper.run(FabricConnectionWrapper.java:158)
	at com.fusesource.ide.fabric.activemq.navigator.ActiveMQNodeProvider.provide(ActiveMQNodeProvider.java:49)
	at com.fusesource.ide.jmx.core.tree.NodeUtils.enrichRootNode(NodeUtils.java:85)
	at com.fusesource.ide.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:77)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper.loadRoot(FabricConnectionWrapper.java:129)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper.loadChildren(FabricConnectionWrapper.java:145)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper.loadChildren(FabricConnectionWrapper.java:141)
	at com.fusesource.rider.commons.tree.RefreshableNode.refresh(RefreshableNode.java:20)
	at com.fusesource.ide.fabric.navigator.jmx.FabricConnectionWrapper.connect(FabricConnectionWrapper.java:91)
	at com.fusesource.ide.jmx.core.ConnectJob.run(ConnectJob.java:32)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.ClassNotFoundException: org.apache.activemq.broker.jmx.QueueViewMBean
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	... 14 more

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Claus Ibsen added a comment - 16/Mar/12 02:05 PM
I get the exception, when I right click on the JMX in the broker1 -> JMX in the Fabric Explorer, and select connect.
Normally Fuse IDE will auto connect if you select the JMX node, as it shows a little expand triangle, that you just open.

[ Permlink | « Hide ]
Lars Heinemann added a comment - 28/Mar/12 05:44 PM
should be fixed now with James latest patch.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators