[jboss-jira] [JBoss JIRA] (JBJMX-114) Access mbean deployed in Jboss 4.0 from Jboss 7.1 server

[Prashant Srivastava (JIRA)]

Prashant Srivastava created JBJMX-114:
-----------------------------------------

             Summary: Access mbean deployed in Jboss 4.0 from Jboss 7.1 server
                 Key: JBJMX-114
                 URL: https://issues.jboss.org/browse/JBJMX-114
             Project: JBoss JMX
          Issue Type: Feature Request
            Reporter: Prashant Srivastava


One application is deployed in JBOSS 4.0.5. The monitoring application is deployed in jboss 7.1.0. Both are deployed in separate machines in the same network. We can not access the manged bean published by jboss 4.0.5 from jboss 7.1.0. Tried both the JNP and remoting. I think remoting is the suggested approach for jboss 7. But in this case the following exception is coming..
Root exception is java.lang.RuntimeException: Operation failed with status WAITING

Following is the configuration .. 

Hashtable<String, String> envProps = new Hashtable<String, String>();
envProps.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
envProps.put(Context.SECURITY_CREDENTIALS, "<<password>>"); 
envProps.put(Context.SECURITY_PRINCIPAL, "<<user>>"); // application-realm user of the jboss 7 server
String url = "remote://" + <<ip of the jboss 4.0 server where the mbeans are deployed>> + ":4447";
envProps.put(Context.PROVIDER_URL, url);

envProps.put("org.jboss.remoting-jmx.timeout", "86400");
InitialContext context = new InitialContext(envProps);
return (MBeanServerConnection)context.lookup("jmx/rmi/RMIAdaptor");

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