Just to be clear on the severity, we will hit this issue with the embedded agent when it
tries connect to *any* standard MBean server running in another JVM.
On Feb 18, 2014, at 1:46 PM, John Mazzitelli <mazz(a)redhat.com> wrote:
An FYI regarding an very bad issue I hit while integrating the
embedded agent in the RHQ Server:
I just ran into something John Sanda hit a while ago. This time its involving the
embedded agent running inside RHQ Server (and I assume the same will happen just running
the agent in any EAP instance or the Host Controller). We are hitting this error when
trying to get the availability of the storage node:
javax.naming.NameNotFoundException: rmi://localhost:7299/jmxrmi
A quick google brings up this:
https://issues.jboss.org/browse/WFLY-794
which leads me to the related RHQ BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=951993
Here's some WildFly threads on this:
https://community.jboss.org/message/806331#806331
https://community.jboss.org/message/721471#721471
https://issues.jboss.org/browse/AS7-2138 (John Sanda has some comments in here)
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel