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.
I'm in the same boat, getting these '[PropagationContextManager] jboss-atx: unknown Tx Propagation Context' messages.
Anyone come to understand them yet?
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.