2 Replies Latest reply on Oct 29, 2009 5:19 PM by Jim Johnson

    4.2.3 Server, 5.1.0 client EJB issue.

    Jim Johnson Newbie

      Hello. I'm currently attempting to use an existing JBoss 4.2.3 instance which has some Remote EJBs with a JBoss 5.1.0 instance as the client. The EJBs are looked up via the standard InitialContext methodology. When my client is a 4.2.3 instance everything works great. When I try to do the lookup from my 5.1.0 instance I get an exception:

      javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.ejb3.JBossProxy (no security manager: RMI class loader disabled)]
       atorg.jnp.interfaces.NamingContext.lookup(NamingContext.java:845)
       at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
       at javax.naming.InitialContext.lookup(InitialContext.java:392)
      ...
      


      I've been researching solutions to this problem. Everything I've seen though, the fix has been to put the client-all.jar into the classpath of the client. I don't think that solution applies to my situation since I can look up EJBs using @EJB injection between 2 jboss 5 instances just fine. The JBoss 5.1.0 AS should have some form of the EJB client jars in its classpath. Also, adding the 4.2.3 client-all.jar into a 5.1.0 server seems like a bad idea.

      I tried looking for a compatibility matrix, but only found one that shows the compatibility between JBoss 3 & JBoss 4 versions. Does anyone know if using 4.2.3 server w/ a 5.1.0 is supported? Is there some sort of setting/configuration I need to do to make this work? Or is this something that is simply not supported? I have other ways to deal with the RMI but they require implementation time so using the existing plumbing would be ideal. Thank you for any insight anyone can provide.