Description
This bug sounds similar to those already reported under JBAS-1443 and JBAS-1495.
Using two JBoss instances in a peer-to-peer set-up, the same EJB packages are deployed on both. In this case, both instances will show the same Session Bean, bound by the same name in their respective JNDI namespace. Invoking the remote Session Bean from one instance, results in the call being 'rerouted' to the local Session Bean. The problem disappears if the Beans are given different names. This could to be a side effect of some optimization mechanism, to accelerate operations confined within the same VM.
Please elaborate on this issue, as it would appear that the previous bug reports were closed. In that case, kindly confirm if this behaviour will or will not be changed.
A demonstration project is available on request.