Issue

• While connecting to an MBean Server deployed on another JBoss instance, the following exception is encountered.

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/AppOne].[jsp]] (http-/10.10.10.10:8080-1) Servlet.service() for servlet jsp threw exception: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://10.10.10.10:9999/jmxrmi -- service jboss.naming.context.java.rmi:."10.10.10.10:9999".jmxrmi
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:357) [rt.jar:1.7.0_05]
    at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267) [rt.jar:1.7.0_05]
    at aaa.HeapAndNonHeapMonitoring.connectWRONG(HeapAndNonHeapMonitoring.java:25) [classes:]
    at org.apache.jsp.wrongOption_jsp._jspService(wrongOption_jsp.java:65)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-2.jar:1.0.1.Final-redhat-2]
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:253) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-2.jar:1.0.1.Final-redhat-2]
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.17.Final-redhat-1.jar:]
    at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
Caused by: javax.naming.NameNotFoundException: rmi://10.10.10.10:9999/jmxrmi -- service jboss.naming.context.java.rmi:."10.10.10.10:9999".jmxrmi
    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
    at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:120)
    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:215)
    at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_05]
    at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1924) [rt.jar:1.7.0_05]
    at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1891) [rt.jar:1.7.0_05]
    at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:274) [rt.jar:1.7.0_05]
    ... 22 more

• Scenario "JBoss-A" has a WAR deployed in it which internally tries to access the MBeans deployed on "JBoss-B" then the above exception is encountered.