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

[dvdpurcell]

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

[umakemuheadhurt]

Did you get anywhere with this, ie JBoss 4.0.3 talking to 4.2.2?

We facing the same situation and were also wondering what 'you must use the legacy rmi invokers' means...

According to the compatibility matrix, 4.0.4 can talk to 4.2.2 with a compatibility mode flag, and we're assuming 4.0.3SP1 can talk to 4.0.4, since that interaction is not specifically spelled out. So we're thinking about moving legacy apps to 4.0.4 to help creep out of this backwards compatibility hole JBoss has dug for us... Also assuming moving from 4.0.3SP1 to 4.0.4 is relatively trivial.

[jaikiran]

One user reported here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=129728 that he got this running

[deckrider]

I'm in the same boat, getting these '[PropagationContextManager] jboss-atx: unknown Tx Propagation Context' messages.

Anyone come to understand them yet?

[deckrider]

I'm in the same boat, getting these '[PropagationContextManager] jboss-atx: unknown Tx Propagation Context' messages. It seems that I've made progress however. I've uncommented the following section of jboss-4.2.3.GA/server/all/conf/jboss-service.xml headed by this text:

 <!--
 | The fast in-memory transaction manager.
 | Deprecated in JBossAS v4.2. Use JBossTS JTA instead.
 -->

And then I've commented out the section headed by this text:

<!-- JBoss Transactions JTA -->

I think this effectively reverts to the 4.0.3SP1 transaction manager.