[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen updated AS7-2138: ---------------------------------- Description: When trying to create a MBeanServerConnection from within an EJB a "javax.naming.NameNotFoundException" is thrown. When executed as a standalone Java the same code works fine. To verify that it works as a standalone Java process run "java -cp jmx-test.jar com.example.JMXConnectionBean" (with AS7 running on the same machine). Full stack trace: {code} Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26] at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152) ... 9 more Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209) at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26] ... 37 more {code} was: When trying to create a MBeanServerConnection from within an EJB a "javax.naming.NameNotFoundException" is thrown. When executed as a standalone Java the same code works fine. Full stack trace: {code} Caused by: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:340) [:1.6.0_26] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) [:1.6.0_26] at com.example.JMXConnectionBean.init(JMXConnectionBean.java:28) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_26] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_26] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_26] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_26] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:70) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.ManagedReferenceInterceptor.processInvocation(ManagedReferenceInterceptor.java:53) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:44) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor$CustomSessionInvocationContext.proceed(SessionInvocationContextInterceptor.java:126) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:211) at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:313) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:56) at org.jboss.as.ejb3.tx.SingletonLifecycleCMTTxInterceptor.processInvocation(SingletonLifecycleCMTTxInterceptor.java:42) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ejb3.component.session.SessionInvocationContextInterceptor.processInvocation(SessionInvocationContextInterceptor.java:71) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:287) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.0.Final.jar:1.1.0.Final] at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:152) ... 9 more Caused by: javax.naming.NameNotFoundException: rmi://127.0.0.1:1090/jmxrmi -- service jboss.naming.context.java.rmi:."127.0.0.1:1090".jmxrmi at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:87) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:173) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:47) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:209) at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1888) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1858) [:1.6.0_26] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:257) [:1.6.0_26] ... 37 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski reassigned AS7-2138: --------------------------------------- Assignee: Bartosz Baranowski -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen commented on AS7-2138: --------------------------------------- Personally I wouldn't mind a custom context factory to do this. I assume this would be configured by setting "Context.INITIAL_CONTEXT_FACTORY=CustomFactory" in the environment passed to JMXConnectorFactory? If this is the resolution of this issue I would greatly appreciate some help in creating that as I wouldn't have a clue where to start. I've tried to experiment with making sure the SUN JMX provider is available on the classpath and passing the initial context factory used when ran outside AS7, but this gave me some other problems. Can't remember exactly what the exception/problems where, I believe it was something about not finding the Registry on localhost:1099. However, with all that said it would be much nicer if this worked out of the box. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen commented on AS7-2138: --------------------------------------- At first glance I don't know how to do that, and it does seem like this is a bug in AS7, so it would be nice if it could be fixed properly? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2138: ---------------------------------- Component/s: JMX -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-2138: ----------------------------------- {quote} This is fixed in 7.1.0.Final {quote} I'll close this then. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darius Schier commented on AS7-2138: ------------------------------------ We've tried it with Thunder (7.1.0) but get exactly the same error message if we try to contact an external JMX-Server (activemq). In SE environment, it works as expected. We also tried the workaround (overriding rmiURLContextFactory returning the object directly and setting it in the properties as suggested), unfortuanately with the same behaviour. Would you mind to reopen this issue, please? {noformat} javax.naming.NameNotFoundException: rmi://tmq.int.saarstahl.de:1099/jmxrmi -- service jboss.naming.context.java.rmi:."tmq.int.saarstahl.de:1099".jmxrmi at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:97) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:113) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:213) at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_30] at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1886) [rt.jar:1.6.0_30] at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1856) [rt.jar:1.6.0_30] at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:255) [rt.jar:1.6.0_30] ... 60 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] jaikiran pai reopened AS7-2138: ------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen commented on AS7-2138: --------------------------------------- I didn't consider the fact that it would still not work when connecting to a JMX server using the standard RMI connector. The reason it works for me in 7.1.0.Final is that JBoss uses the remoting-jmx JSR-160 connector now, which basically bypasses the problem when connecting to another JBoss server. However, the problem is still very much there when connecting to any other servers/apps over the standard RMI connector. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski commented on AS7-2138: ----------------------------------------- If this is a blocker I can dig up my workaround code and check if it still works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-2138: --------------------------------------- We do not support the RMI URLs - if a remote connection is needed the remoting-jmx protocol should be used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen commented on AS7-2138: --------------------------------------- Bartosz - If the workaround works I'd be interested in it as well -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-2138: --------------------------------------- Just looked at the attachment again, it does appear that attachment shows a call that used to work from the outside but no attachment to reproduce the error - does anyone have one they can attach? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen edited comment on AS7-2138 at 2/24/12 9:13 AM: ---------------------------------------------------------------- Darran - this issue was created prior to remoting-jmx hence why the example code works(ed) as a standalone client. The description also clearly states that it works fine from a standalone application, but not a EJB (and since this is a JBoss 7 issue it would be reasonable to guess that the EJB was deployed to JBoss?). If the example is modified to use remoting-jmx it works fine from within an EJB and as a standalone Java app. This makes it possible to open a JMX connection from within one AS 7.1.0.Final server to another AS 7.1.0.Final server using remoting-jmx. However, it is still not possible to open a JMX connection from within one AS 7.1.0.Final server to a older JBoss server (or any other application/server using a standard RMI server). The bug that was identified by Bartosz for a while ago is still valid, just simply not in effect when connection from a AS 7.1.0.Final server to another AS 7.1.0.Final. was (Author: stianst): Darran - this issue was created prior to remoting-jmx hence why the example code works(ed) as a standalone client. The description also clearly states that it works fine from a standalone application, but not a EJB (and since this is a JBoss 7 issue it would be reasonable to guess that the EJB was deployed to JBoss?). If the example is modified to use remoting-jmx it works fine from within an EJB and as a standalone Java app. This makes it possible to open a JMX connection from within one AS 7.1.0.Final server to another AS 7.1.0.Final server using remoting-jmx. However, it is still not possible to open a JMX connection from within one AS 7.1.0.Final server to a older JBoss server (or any other application/server using a standard RMI server). The bug that was identified by Bartosz for a while ago is still valid, just simple not in effect when connection from a AS 7.1.0.Final server to another AS 7.1.0.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Stian Thorgersen updated AS7-2138: ---------------------------------- Attachment: JmxClient.java JmxServer.java JmxServer - starts a JMX RMI server JmxClient - used to check that the server is running With the JmxServer running the original attached bean (or jar) can be deployed to JBoss to reproduce the issue on 7.1.0.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] SBS JIRA Integration updated AS7-2138: -------------------------------------- Forum Reference: https://community.jboss.org/message/721471#721471 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned AS7-2138: ------------------------------------- Assignee: Darran Lofthouse (was: Bartosz Baranowski) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-2138: ---------------------------------- Assignee: Bartosz Baranowski (was: Darran Lofthouse) Forum Reference: https://community.jboss.org/message/721471#721471 (was: https://community.jboss.org/message/721471#721471) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski updated AS7-2138: ------------------------------------ Workaround Description: {code:title=Connector.java|borderStyle=solid} JMXConnector connector = null; MBeanServerConnection connection = null; try { String urlString = /* System.getProperty("jmx.service.url", */JMXConnectorTestCase.SERVICE_URI/* ) */; JMXServiceURL serviceURL = new JMXServiceURL(urlString); Map<String, String> env = new HashMap<String, String>(); env.put(InitialContext.INITIAL_CONTEXT_FACTORY, RMIContextFactory.class.getName()); connector = JMXConnectorFactory.connect(serviceURL, env); connection = connector.getMBeanServerConnection(); } finally { if (connector != null) { connector.close(); } } {code} {code:title=RMIContextFactory.java|borderStyle=solid} import java.util.Hashtable; import javax.naming.Context; import javax.naming.NamingException; import javax.naming.spi.InitialContextFactory; import com.sun.jndi.url.rmi.rmiURLContext; public class RMIContextFactory implements InitialContextFactory{ /* (non-Javadoc) * @see javax.naming.spi.InitialContextFactory#getInitialContext(java.util.Hashtable) */ @Override public Context getInitialContext(Hashtable<?, ?> environment) throws NamingException { return new rmiURLContext(environment); } } {code} Also this will require small modification of sun.jdk module, to export 'com.sun.jndi.url.rmi' path(or you will have to provide your own impl of rmiContext :) ), since by default this module exports 'com.sun.jndi.url' and 'com.sun.jndi.url.ldap', iirc. So, edit: *jboss-as/build/src/main/resources/modules/sun/jdk/main/main.xml* and one statement: *<path name="com/sun/jndi/url/rmi"/>*, it should look like this: {code:xml} <module xmlns="urn:jboss:module:1.1" name="sun.jdk"> <resources> <!-- currently jboss modules has not way of importing services from classes.jar so we duplicate them here --> <resource-root path="service-loader-resources"/> </resources> <dependencies> <system export="true"> <paths> <path name="com/sun/script/javascript"/> <path name="com/sun/jndi/dns"/> <path name="com/sun/jndi/ldap"/> <path name="com/sun/jndi/url"/> <path name="com/sun/jndi/url/rmi"/> <path name="com/sun/jndi/url/dns"/> <path name="com/sun/security/auth"/> <path name="com/sun/security/auth/login"/> <path name="com/sun/security/auth/module"/> <path name="sun/misc"/> <path name="sun/io"/> <path name="sun/nio"/> <path name="sun/nio/ch"/> <path name="sun/security"/> <path name="sun/security/krb5"/> <path name="sun/util"/> <path name="sun/util/calendar"/> <path name="sun/security/provider"/> <path name="META-INF/services"/> </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> {code} Now NOTE: this will make that initial context to be usable ONLY for RMI lookups. was:Provide properties to InitialContext which make it create context factory which returns rmiURLContext, check http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-... Forum Reference: https://community.jboss.org/message/721471#721471 (was: https://community.jboss.org/message/721471#721471) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Bartosz Baranowski updated AS7-2138: ------------------------------------ Workaround Description: {code:title=Connector.java|borderStyle=solid} JMXConnector connector = null; MBeanServerConnection connection = null; try { String urlString = "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi"; JMXServiceURL serviceURL = new JMXServiceURL(urlString); Map<String, String> env = new HashMap<String, String>(); env.put(InitialContext.INITIAL_CONTEXT_FACTORY, RMIContextFactory.class.getName()); connector = JMXConnectorFactory.connect(serviceURL, env); connection = connector.getMBeanServerConnection(); } finally { if (connector != null) { connector.close(); } } {code} {code:title=RMIContextFactory.java|borderStyle=solid} import java.util.Hashtable; import javax.naming.Context; import javax.naming.NamingException; import javax.naming.spi.InitialContextFactory; import com.sun.jndi.url.rmi.rmiURLContext; public class RMIContextFactory implements InitialContextFactory{ /* (non-Javadoc) * @see javax.naming.spi.InitialContextFactory#getInitialContext(java.util.Hashtable) */ @Override public Context getInitialContext(Hashtable<?, ?> environment) throws NamingException { return new rmiURLContext(environment); } } {code} Also this will require small modification of sun.jdk module, to export 'com.sun.jndi.url.rmi' path(or you will have to provide your own impl of rmiContext :) ), since by default this module exports 'com.sun.jndi.url' and 'com.sun.jndi.url.ldap', iirc. So, edit: *jboss-as/build/src/main/resources/modules/sun/jdk/main/main.xml* and one statement: *<path name="com/sun/jndi/url/rmi"/>*, it should look like this: {code:xml} <module xmlns="urn:jboss:module:1.1" name="sun.jdk"> <resources> <!-- currently jboss modules has not way of importing services from classes.jar so we duplicate them here --> <resource-root path="service-loader-resources"/> </resources> <dependencies> <system export="true"> <paths> <path name="com/sun/script/javascript"/> <path name="com/sun/jndi/dns"/> <path name="com/sun/jndi/ldap"/> <path name="com/sun/jndi/url"/> <path name="com/sun/jndi/url/rmi"/> <path name="com/sun/jndi/url/dns"/> <path name="com/sun/security/auth"/> <path name="com/sun/security/auth/login"/> <path name="com/sun/security/auth/module"/> <path name="sun/misc"/> <path name="sun/io"/> <path name="sun/nio"/> <path name="sun/nio/ch"/> <path name="sun/security"/> <path name="sun/security/krb5"/> <path name="sun/util"/> <path name="sun/util/calendar"/> <path name="sun/security/provider"/> <path name="META-INF/services"/> </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> {code} Now NOTE: this will make that initial context to be usable ONLY for RMI lookups. was: {code:title=Connector.java|borderStyle=solid} JMXConnector connector = null; MBeanServerConnection connection = null; try { String urlString = /* System.getProperty("jmx.service.url", */JMXConnectorTestCase.SERVICE_URI/* ) */; JMXServiceURL serviceURL = new JMXServiceURL(urlString); Map<String, String> env = new HashMap<String, String>(); env.put(InitialContext.INITIAL_CONTEXT_FACTORY, RMIContextFactory.class.getName()); connector = JMXConnectorFactory.connect(serviceURL, env); connection = connector.getMBeanServerConnection(); } finally { if (connector != null) { connector.close(); } } {code} {code:title=RMIContextFactory.java|borderStyle=solid} import java.util.Hashtable; import javax.naming.Context; import javax.naming.NamingException; import javax.naming.spi.InitialContextFactory; import com.sun.jndi.url.rmi.rmiURLContext; public class RMIContextFactory implements InitialContextFactory{ /* (non-Javadoc) * @see javax.naming.spi.InitialContextFactory#getInitialContext(java.util.Hashtable) */ @Override public Context getInitialContext(Hashtable<?, ?> environment) throws NamingException { return new rmiURLContext(environment); } } {code} Also this will require small modification of sun.jdk module, to export 'com.sun.jndi.url.rmi' path(or you will have to provide your own impl of rmiContext :) ), since by default this module exports 'com.sun.jndi.url' and 'com.sun.jndi.url.ldap', iirc. So, edit: *jboss-as/build/src/main/resources/modules/sun/jdk/main/main.xml* and one statement: *<path name="com/sun/jndi/url/rmi"/>*, it should look like this: {code:xml} <module xmlns="urn:jboss:module:1.1" name="sun.jdk"> <resources> <!-- currently jboss modules has not way of importing services from classes.jar so we duplicate them here --> <resource-root path="service-loader-resources"/> </resources> <dependencies> <system export="true"> <paths> <path name="com/sun/script/javascript"/> <path name="com/sun/jndi/dns"/> <path name="com/sun/jndi/ldap"/> <path name="com/sun/jndi/url"/> <path name="com/sun/jndi/url/rmi"/> <path name="com/sun/jndi/url/dns"/> <path name="com/sun/security/auth"/> <path name="com/sun/security/auth/login"/> <path name="com/sun/security/auth/module"/> <path name="sun/misc"/> <path name="sun/io"/> <path name="sun/nio"/> <path name="sun/nio/ch"/> <path name="sun/security"/> <path name="sun/security/krb5"/> <path name="sun/util"/> <path name="sun/util/calendar"/> <path name="sun/security/provider"/> <path name="META-INF/services"/> </paths> <exports> <include-set> <path name="META-INF/services"/> </include-set> </exports> </system> </dependencies> </module> {code} Now NOTE: this will make that initial context to be usable ONLY for RMI lookups. Forum Reference: https://community.jboss.org/message/721471#721471 (was: https://community.jboss.org/message/721471#721471) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2138?page=com.atlassian.jira.plugin.s... ] Darius Schier commented on AS7-2138: ------------------------------------ Works like a charm, thank you for the workaround Bartosz! Just one tiny correction for running jboss installations: the file is found under <jboss-as-7.1.0.Final>/modules/sun/jdk/main and is called module.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira