This means that EJB's will not share the same authentication context as the naming provider so invocations on looked up EJB's can fail.Hello
Original report from Michal:
The failures are related to remote EJB invocation from EJB client using WildFly Naming Context appearing with latest release of JBoss EJB Client (obtained from org.jboss.eap:wildfly-ejb-client-bom:7.1.0.GA-redhat-8 Maven artifact). As of now, we have not been able to isolate a reliable reproducer yet and we are not sure if the issue is caused by misconfiguration, environment or if it is a regression.
The offending test results can be accessed at [1] (the "wildfly-naming-client" part of the matrix). The test cases themselves are available at [2].
[1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7x-ejb-client-qa-tests/96/testReport/
[2] http://git.app.eng.bos.redhat.com/git/jbossqe/eap-tests-ejb.git/tree/ejb-client-qa-tests
- incorporates
-
WFNC-49 Remote naming no longer unmarshals in the context of a naming provider
-
- Resolved
-
- is caused by
-
WFNC-48 Add support for automatic retry when multiple provider URIs are specified.
-
- Resolved
-
- is incorporated by
-
JBEAP-13573 Upgrade WildFly Naming Client to 1.0.7.Final
-
- Closed
-