Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-13567

Remote naming no longer unmarshals in the context of a naming provider

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.CR4
    • 7.1.0.CR3
    • EJB
    • None

    Description

      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

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFNC-49 Remote naming no longer unmarshals in the context of a naming provider

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is caused by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFNC-48 Add support for automatic retry when multiple provider URIs are specified.

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-13573 Upgrade WildFly Naming Client to 1.0.7.Final

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: