Invoking a remote Session Bean results in call to locally registered Session Bean. -----------------------------------------------------------------------------------
Key: JBAS-1606 URL: http://jira.jboss.com/jira/browse/JBAS-1606 Project: JBoss Application Server Type: Bug Components: EJBs, Naming Versions: JBossAS-4.0.1 SP1 Reporter: Dann Martens Priority: Minor 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development