from the agent: java.lang.ClassCastException: javax.management.ObjectName incompatible with javax.management.ObjectName at org.mc4j.ems.impl.jmx.connection.DConnection.loadSynchronous(DConnection.java:147) at org.rhq.plugins.jbossas.JBossASServerComponent.loadConnection(JBossASServerComponent.java:1 030) at org.rhq.plugins.jbossas.JBossASServerComponent.start(JBossASServerComponent.java:237) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContaine r.java:525) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690) at java.lang.Thread.run(Thread.java:810) Switching back to the straight jrmp invoker unpukes this. (let me know if this is jopr, I'm not real clear on the beginning and end of each)
Btw the reason that is important is in these releases of jbas some pretty ugly bugs prevent you from changing the bind address of the invoker without changing the bind address for all of jboss (meaning it tries to hit the ethernet).
..where the pooled invoker obeys and plays nice. I blame bill burke...whether he coded that or not.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2488
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
Triaged 5-Oct