This content has been marked as final. 
    
Show                 5 replies
    
- 
        1. Re: JMX bean creating InitialContext: Works from JMX consoljaikiran Dec 6, 2008 5:10 AM (in response to dasmith836)Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory] 
 You need the jbossall-client .jar in the client classpath. You can find that jar in %JBOSS_HOME%/client folder. Which version of JBoss are you using? For JBoss-5, you will also have to add additional jar files which are listed in the MANIFEST.MF file of jbossall-client.jar
- 
        2. Re: JMX bean creating InitialContext: Works from JMX consoldasmith836 Dec 8, 2008 11:39 AM (in response to dasmith836)Jboss 4.2.2 
 On the client? This exception is happening on the server, NOT on the client.
- 
        3. Re: JMX bean creating InitialContext: Works from JMX consoldasmith836 Dec 8, 2008 1:38 PM (in response to dasmith836)TO CLARIFY: 
 the exception
 javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
 is occurring on the server, not on the client. I can watch it happen using IDEA remote debugging on the JBoss instance. I'm wondering if there is a class loader issue, since the RMI access takes a much different code path than the JMX console does.
- 
        4. Re: JMX bean creating InitialContext: Works from JMX consoldasmith836 Dec 17, 2008 11:41 AM (in response to dasmith836)Still haven't found a solution to this - any love here? 
- 
        5. Re: JMX bean creating InitialContext: Works from JMX consoldasmith836 Jan 12, 2009 4:48 PM (in response to dasmith836)(bump) 
 
    