[jboss-jira] [JBoss JIRA] (AS7-4253) TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules

[ https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s... ] Steffen Wollscheid updated AS7-4253: ------------------------------------ Attachment: call-remote-ejb-with-cascaded-osgi-modules.zip The attachment call-remote-ejb-with-cascaded-osgi-modules.zip contains a complete scenario to reproduce the problem: All projects can be built using the root pom.xml and installed into jboss with the install.cli file using jboss-cli.bat (and uninstalled using uninstall.cli) The bundles ejb-accessor-osgi and cascaded-accessor-osgi expose jmx beans which have operations to trigger remote ejb lookups. all lookups will be done in ejb-accessor-osgi. jmx bean calls to cascaded-accessor-osgi will delegate the call to ejb-accessor-osgi. The useInitialContextFromJNDIContext*-methods will only work, when org.apache.aries.jndi is installed, but are not necessary for the demonstration of the problem. Using the jmx bean in ejb-accessor-osgi will always produce success, where as using the jmx bean in cascaded will only result in success when calling the *TCCLAwareVersion methods, which change the TCCL. The others will result in ClassNotFoundExceptions. The jboss-ejb-client.xml in ejb-accessor-osgi tries to use 'remote-ejb-connection'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira