Uploaded image for project: 'WildFly Naming Client'
  1. WildFly Naming Client
  2. WFNC-55

Naming Client must always set thread context class loader

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.0.11.Final
    • 1.0.10.Final
    • None

    Description

      If naming client doesn't set TCCL various random modules may be used for remoting invocations. Setting TCCL ensures naming classloader is always used.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. WFLY-10394 Lookup using remote-naming context does not work in WildFly 13

          • 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.
          • Closed

          Activity

            People

              ropalka Richard Opalka
              ropalka Richard Opalka
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: