4 Replies Latest reply on Aug 25, 2008 6:44 PM by deckrider deckrider

    ejb2 call from 4.0.3 client to 4.2.2 server - how to configu

    David Purcell Newbie

      Hello,
      We're trying to access an ejb(2) deployed on a jboss 4.2.2 server from a client on jboss 4.0.3SP1. According to: http://wiki.jboss.org/wiki/JBossVersionCompatibilityMatrix, 'you must use the legacy rmi invokers' in this case. We weren't sure how to do that, but digging into some jboss remoting jira tickets, we saw that testers for these compatibility issues were basically replacing unified-invoker references with rmi-invoker references in their standardjboss.xml file (basically replacing the 4.2.2's standardjboss.xml with that from 4.0.3). Trying that, it worked in some instances, but we've now come across this error:

      [on client] java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.invocation.JBossLazyUnmarshallingException (no security manager: RMI class loader disabled)

      [on server] ERROR [PropagationContextManager] jboss-atx: unknown Tx Propagation Context

      I fear I'm barking up the wrong tree. I posted this question to the Remoting forum (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136830), and they suggested it was a question that belonged here. Anyone know how to go about 'you must use the legacy rmi invokers'?

      Thanks in advance,

      David