[JBoss JIRA] (AS7-4253) TCCL used by EJBNamingContext is wrong when callstack passes through multiple OSGi modules
5:40 a.m.
Thomas Diesler created AS7-4253:
-----------------------------------
Summary: TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: jaikiran pai
Fix For: 7.2.0.Alpha1
--
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
10:39 a.m.
[
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'.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: jaikiran pai
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip
--
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
4:28 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Steffen Wollscheid updated AS7-4253:
------------------------------------
Attachment: isolated-test-case.zip
Attached isolated-test-case.zip, which wraps the scenario into one project. The project
contains one Arquillian test case to demonstrate the problem.
To run the test just unzip, adapt the jbossHome property in
src/main/resource/arquillian.xml and run "mvn test".
The test assumes that the jboss is running as 127.0.0.1 with the native management
interace port 9999 (default).
Also the ejb remote calls are done without any credentials so remove the security-realm
attribute from the remoting-subsystem.
The test case contains four single tests, which all run using Arquillian @RunAsClient
- test -> osgiB -> ejb, tccl-unaware, which succeeds
- test -> osgiB -> ejb, tccl-awarem, which succeeds
- test -> osgiA -> osgiB -> ejb, tccl-aware, which succeeds
- test -> osgiA -> osgiB -> ejb, tccl-unaware, which fails
The calls from test to osgiX are done usig jmx. The call osgiA ot osgiB is an OSGi service
call.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: jaikiran pai
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
5:34 p.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-4253.
---------------------------------
Fix Version/s: (was: 7.2.0.Alpha1)
Resolution: Won't Fix
As far as I can see this is not a bug. The ejb: namespace is a client side namespace, it
does no server lookups by design (except when looking up SFSB's).
If you are attempting to lookup an EJB remote interface that the TCCL cannot load then
there is simply no way for JNDI to magically figure out the correct class loader to use.
This is compounded by the fact that when using remote EJB's it is actually common to
have the remote interfaces defined in several different deployments, so there are actually
several different class loaders that are 'correct'. We need some mechanism to
determine which one to use, and the standard way to do this in java is the TCCL.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: jaikiran pai
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:31 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Steffen Wollscheid commented on AS7-4253:
-----------------------------------------
@Stuart
A few notes on your comment:
A. It does not matter, how many deployments the interfaces are defined in -- all
interfaces are imported into the calling bundle's classloader via osgi, so code in the
bundle has every reason to expect the interface classes to be known, whenever it calls a
method - and that is what happens in all cases, EXCEPT when the method called uses the
TCCL as classloader.
B. In an EJB application it is not uncommon for an application server to act as a remote
EJB client.
C. I do not expect magic from the JNDI, i expect it to work reliably. The current
programming stops the TCCL from containing the classes, which are currently executed on
that thread -- this is a BUG. Period.
The bug lies not necessarily with JNDI - in the originial discussion i proposed some kind
of interceptor updating the TCCL whenever a thread enters a bundle, perhaps using the
class returned from BundleContext.getService().
It's up to you guys to find a solution for this bug -- for a bug it is, and it is not
going to go away by closing this ticket.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: jaikiran pai
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:57 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reopened AS7-4253:
---------------------------------
Assignee: Thomas Diesler (was: jaikiran pai)
IMO, a lookup should work from OSGi if the calling bundle has a wire (i.e. can see) the
EJB remote/local interface. We only have to define what lookup syntax needs to be used.
I'll bring in the failing test and see if I can show how to make it pass.
Steffen/Stuart thanks for the above
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:59 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4253:
-------------------------------------
If you lookup the ejb from java:global JNDI (rather than ejb: ) then it should work no
matter what the current value for the TCCL is, as it has a fall back to the defining
modules class loader.
ejb: has no such fallback, as it is a client side only, and has no way of figuring out the
correct class loader to use other than the TCCL. The only way I can think to work around
this would be some way of passing the class loader to use into the initial context
environment. e.g.
Properties props = new Properties();
props.put("org.jboss.ejb.client.classloader", getClass().getClassLoader());
InitialContext ic = new InitialContext(props);
If this would be helpful then please file a feature request against the EJBCLIENT
project.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:51 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-4253:
--------------------------------
Fix Version/s: 7.2.0.Alpha1
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
5:26 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reassigned AS7-4253:
-----------------------------------
Assignee: (was: Thomas Diesler)
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
9:02 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-4253:
--------------------------------
Assignee: Thomas Diesler
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
5:30 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reassigned AS7-4253:
-----------------------------------
Assignee: Stuart Douglas (was: Thomas Diesler)
Stuart, could you please run
git://github.com/tdiesler/as4253.git
for me. I removed all references to OSGi from this test project and I'm now seeing
{code}
12:14:26,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar"
12:14:27,136 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015870:
Deploy of deployment "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar" was rolled back with
failure message {"JBAS014771: Services with missing/unavailable dependencies"
=>
["jboss.ejb3.dd-based-ejb-client-context.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\"
Missing[jboss.remoting.endpoint.subsystem.outbound-connection.remote-ejb-connection]","jboss.deployment.unit.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\".INSTALL
Missing[JBAS014861: <one or more transitive dependencies>]"]}
12:14:27,162 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877:
Stopped deployment ejb-accessor-osgi-0.0.1-SNAPSHOT.jar in 26ms
{code}
I want to make sure that this works without OSGi before I look further. Cheers.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Stuart Douglas
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
5:30 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-4253 at 7/9/12 6:29 AM:
-------------------------------------------------------------
Stuart, could you please run
https://github.com/tdiesler/as4253
for me. I removed all references to OSGi from this test project and I'm now seeing
{code}
12:14:26,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar"
12:14:27,136 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015870:
Deploy of deployment "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar" was rolled back with
failure message {"JBAS014771: Services with missing/unavailable dependencies"
=>
["jboss.ejb3.dd-based-ejb-client-context.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\"
Missing[jboss.remoting.endpoint.subsystem.outbound-connection.remote-ejb-connection]","jboss.deployment.unit.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\".INSTALL
Missing[JBAS014861: <one or more transitive dependencies>]"]}
12:14:27,162 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877:
Stopped deployment ejb-accessor-osgi-0.0.1-SNAPSHOT.jar in 26ms
{code}
I want to make sure that this works without OSGi before I look further. Cheers.
was (Author: thomas.diesler):
Stuart, could you please run
git://github.com/tdiesler/as4253.git
for me. I removed all references to OSGi from this test project and I'm now seeing
{code}
12:14:26,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar"
12:14:27,136 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015870:
Deploy of deployment "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar" was rolled back with
failure message {"JBAS014771: Services with missing/unavailable dependencies"
=>
["jboss.ejb3.dd-based-ejb-client-context.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\"
Missing[jboss.remoting.endpoint.subsystem.outbound-connection.remote-ejb-connection]","jboss.deployment.unit.\"ejb-accessor-osgi-0.0.1-SNAPSHOT.jar\".INSTALL
Missing[JBAS014861: <one or more transitive dependencies>]"]}
12:14:27,162 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877:
Stopped deployment ejb-accessor-osgi-0.0.1-SNAPSHOT.jar in 26ms
{code}
I want to make sure that this works without OSGi before I look further. Cheers.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Stuart Douglas
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
10:04 p.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas commented on AS7-4253:
-------------------------------------
It looks like that file was copied straight from the multi node test suite, however that
test suite runs two servers, and sets up the connection between them as part of the
build.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
10:04 p.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas reassigned AS7-4253:
-----------------------------------
Assignee: Thomas Diesler (was: Stuart Douglas)
https://github.com/tdiesler/as4253/blob/master/src/test/resources/accesso...
This is referencing a connection to another server that does not exist, which is why you
are getting this missing dependency.
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:37 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-4253:
--------------------------------
Attachment: as4253.zip
Attached a working setup
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:39 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler resolved AS7-4253.
---------------------------------
Resolution: Done
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:43 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reopened AS7-4253:
---------------------------------
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:47 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-4253 at 7/10/12 3:45 AM:
--------------------------------------------------------------
Done. working test project attached
{code}
Running demo.experimental.IsolatedTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.743 sec
{code}
{code}
09:26:10,710 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876:
Starting deployment of "interfaces-osgi-0.0.1-SNAPSHOT.jar"
09:26:10,826 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi
Framework - 2.0.0.CR5
09:26:11,068 INFO [org.jboss.osgi.repository] (MSC service thread 1-4) JBOSGI020400:
Resource added: URLResource[org.apache.felix.eventadmin:1.2.6]
09:26:11,134 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: org.apache.felix.log:1.0.0
09:26:11,147 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: jboss-osgi-logging:1.0.0
09:26:11,171 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
09:26:11,172 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001:
Bundle installed: osgi.enterprise:4.2.0.201003190513
09:26:11,173 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001:
Bundle installed: org.apache.felix.configadmin:1.2.8
09:26:11,364 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011011:
Starting bundles for start level: 1
09:26:11,390 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002:
Bundle started: org.apache.felix.log:1.0.0
09:26:11,452 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002:
Bundle started: org.apache.felix.configadmin:1.2.8
09:26:11,470 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002:
Bundle started: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
09:26:11,494 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002:
Bundle started: jboss-osgi-logging:1.0.0
09:26:11,510 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: demo.experimental.interfaces-osgi:0.0.1.SNAPSHOT
09:26:11,530 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011000: OSGi
Framework started
09:26:11,650 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011002:
Bundle started: demo.experimental.interfaces-osgi:0.0.1.SNAPSHOT
09:26:11,888 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018559:
Deployed "interfaces-osgi-0.0.1-SNAPSHOT.jar"
09:26:12,856 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900:
Content added at location
/home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/a8/5a9dca8c0699394106a49880b8984987194709/content
09:26:12,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876:
Starting deployment of "application-ear-0.0.1-SNAPSHOT.ear"
09:26:12,875 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876:
Starting deployment of "ejb-definition-0.0.1-SNAPSHOT.jar"
09:26:12,916 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: ejb-definition-0.0.1-SNAPSHOT.jar:0.0.0
09:26:13,024 INFO
[org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC
service thread 1-4) JNDI bindings for session bean named CalculatorBean in deployment unit
subdeployment "ejb-definition-0.0.1-SNAPSHOT.jar" of deployment
"application-ear-0.0.1-SNAPSHOT.ear" are as follows:
java:global/application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT/CalculatorBean!demo.experimental.interfaces.RemoteCalculator
java:app/ejb-definition-0.0.1-SNAPSHOT/CalculatorBean!demo.experimental.interfaces.RemoteCalculator
java:module/CalculatorBean!demo.experimental.interfaces.RemoteCalculator
java:jboss/exported/application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT/CalculatorBean!demo.experimental.interfaces.RemoteCalculator
java:global/application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT/CalculatorBean
java:app/ejb-definition-0.0.1-SNAPSHOT/CalculatorBean
java:module/CalculatorBean
09:26:13,171 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011002:
Bundle started: ejb-definition-0.0.1-SNAPSHOT.jar:0.0.0
09:26:13,337 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559:
Deployed "application-ear-0.0.1-SNAPSHOT.ear"
09:26:13,427 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900:
Content added at location
/home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/8c/2fef02a7a18809b999dca054c15cece2fa0a5f/content
09:26:13,434 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar"
09:26:13,449 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001:
Bundle installed: demo.experimental.ejb-accessor-osgi:0.0.1.SNAPSHOT
09:26:13,494 INFO [stdout] (MSC service thread 1-4) MBEANSERVER FOUND
09:26:13,494 INFO [stdout] (MSC service thread 1-4) ************************ REGISTER
**********************
09:26:13,504 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002:
Bundle started: demo.experimental.ejb-accessor-osgi:0.0.1.SNAPSHOT
09:26:13,585 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559:
Deployed "ejb-accessor-osgi-0.0.1-SNAPSHOT.jar"
09:26:13,642 INFO [org.jboss.as.repository] (management-handler-thread - 2) JBAS014900:
Content added at location
/home/tdiesler/git/jboss-as/build/target/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/data/content/52/e80de9d95bfca178c21cfa0d539cd93e541267/content
09:26:13,647 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "cascaded-accessor-osgi-0.0.1-SNAPSHOT.jar"
09:26:13,672 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001:
Bundle installed: demo.experimental.cascaded-accessor-osgi:0.0.1.SNAPSHOT
09:26:13,703 INFO [stdout] (MSC service thread 1-4) MBEANSERVER FOUND
09:26:13,703 INFO [stdout] (MSC service thread 1-4) ************************ REGISTER
CASCADED **********************
09:26:13,706 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011002:
Bundle started: demo.experimental.cascaded-accessor-osgi:0.0.1.SNAPSHOT
09:26:13,788 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559:
Deployed "cascaded-accessor-osgi-0.0.1-SNAPSHOT.jar"
09:26:14,061 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,062 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,062 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,062 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,079 INFO [org.jboss.ejb.client] (pool-3-thread-1) JBoss EJB Client version
1.0.10.Final
09:26:14,084 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,160 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,160 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,160 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,161 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,161 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,230 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,230 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,230 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,231 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,231 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,237 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,237 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,237 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,238 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,238 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,291 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,291 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,291 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.cascaded-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from
Service Module Loader
09:26:14,292 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,292 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,298 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,299 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,299 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.cascaded-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from
Service Module Loader
09:26:14,299 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,300 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,379 INFO [stdout] (pool-3-thread-1) Setting TCCL to
org.jboss.osgi.framework.internal.HostBundleClassLoader@541748428
09:26:14,379 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,379 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,380 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,380 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,380 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,381 INFO [stdout] (pool-3-thread-1) Restoring original TCCL
org.jboss.osgi.framework.internal.HostBundleClassLoader@1548171171
09:26:14,385 INFO [stdout] (pool-3-thread-1) Setting TCCL to
org.jboss.osgi.framework.internal.HostBundleClassLoader@541748428
09:26:14,386 INFO [stdout] (pool-3-thread-1) Start lookup
09:26:14,386 INFO [stdout] (pool-3-thread-1) Bundle Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,387 INFO [stdout] (pool-3-thread-1) Context Classloader: HostBundleClassLoader
for Module "deployment.ejb-accessor-osgi-0.0.1-SNAPSHOT.jar:main" from Service
Module Loader
09:26:14,387 INFO [stdout] (pool-3-thread-1) doing lookup
for:ejb:application-ear-0.0.1-SNAPSHOT/ejb-definition-0.0.1-SNAPSHOT//CalculatorBean!demo.experimental.interfaces.RemoteCalculator
09:26:14,387 INFO [stdout] (pool-3-thread-1) lookup succeeded, calling remote bean
09:26:14,388 INFO [stdout] (pool-3-thread-1) Restoring original TCCL
org.jboss.osgi.framework.internal.HostBundleClassLoader@1548171171
{code}
was (Author: thomas.diesler):
Attached a working setup
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:43 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler reopened AS7-4253:
---------------------------------
Steffen says:
{quote}
I'm afraid the CNFE is precisely what the testcase was about in the first place.
The cascaded-accessor-bundle did not import the RemoteCalculator.class on purpose, because
it does not use it.
RemoteCalculator.class is a interface between the ejb-accessor-bundle (which imports it)
and the ebj-definition ear/jar - as such it is a implementation detail of the
ejb-accessor-bundle.
The CNFE arises from the fact that the TCCL is set to the HostBundleClassLoader of
cascaded-accessor-bundle when the ejb-accessor-bundle calls the ejb on behalf of the
cascaded-accessor-bundle.
{quote}
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
2:43 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-4253 at 7/18/12 3:42 AM:
--------------------------------------------------------------
Steffen says:
{quote}
I'm afraid the CNFE is precisely what the testcase was about in the first place.
The cascaded-accessor-bundle did not import the RemoteCalculator.class on purpose, because
it does not use it.
RemoteCalculator.class is a interface between the ejb-accessor-bundle (which imports it)
and the ebj-definition ear/jar - as such it is a implementation detail of the
ejb-accessor-bundle.
The CNFE arises from the fact that the TCCL is set to the HostBundleClassLoader of
cascaded-accessor-bundle when the ejb-accessor-bundle calls the ejb on behalf of the
cascaded-accessor-bundle.
{quote}
https://community.jboss.org/message/748378#748378
was (Author: thomas.diesler):
Steffen says:
{quote}
I'm afraid the CNFE is precisely what the testcase was about in the first place.
The cascaded-accessor-bundle did not import the RemoteCalculator.class on purpose, because
it does not use it.
RemoteCalculator.class is a interface between the ejb-accessor-bundle (which imports it)
and the ebj-definition ear/jar - as such it is a implementation detail of the
ejb-accessor-bundle.
The CNFE arises from the fact that the TCCL is set to the HostBundleClassLoader of
cascaded-accessor-bundle when the ejb-accessor-bundle calls the ejb on behalf of the
cascaded-accessor-bundle.
{quote}
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
7:06 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-4253:
--------------------------------
Attachment: (was: as4253.zip)
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
7:12 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler updated AS7-4253:
--------------------------------
Attachment: as4253.zip
Removed the RemoteCalculator import
Use java:global/... instead of ejb:...
The InitialContext that you get from the OSGi service lookup is the global default
InitialContext. It has no notion of caller.
I'll consult with David to see if we should register a ServiceFactory instead
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
7:14 a.m.
[
https://issues.jboss.org/browse/AS7-4253?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler resolved AS7-4253.
---------------------------------
Resolution: Done
Done
TCCL used by EJBNamingContext is wrong when callstack passes through
multiple OSGi modules
------------------------------------------------------------------------------------------
Key: AS7-4253
URL: https://issues.jboss.org/browse/AS7-4253
Project: Application Server 7
Issue Type: Bug
Components: EJB, OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.Alpha1
Attachments: as4253.zip, call-remote-ejb-with-cascaded-osgi-modules.zip,
isolated-test-case.zip
--
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
4453
days inactive
4580
days old
22 comments
3 participants
participants (3)
-
Steffen Wollscheid (JIRA) -
Stuart Douglas (JIRA)
-
Thomas Diesler (JIRA)