Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-621

Support legacy slaves when invoking wildcard reads in a domain

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.0.0.Beta6
    • Component/s: Management
    • Labels:
      None

      Description

      This is a follow-on to WFCORE-282.

      The WFCORE-282 solution will not work for requests with address patterns

      /host=*/server=*

      or

      /host=somename/server=*

      if the host named 'somename' is running a WFCORE version prior to 1.0.0.CR1 (or whatever release first has WFCORE-282 introduced.)

      In particular, it won't work with slaves running EAP 6.x.

      The problem is with either of those address patterns the DC will send a request addressed to

      /host=somename/server=*

      to the slave, and the slave will not be able to handle it, as it won't have the WFCORE-282 logic that lets it identify the relevant servers and send requests on to them.

      Potentially this could be fixed by having the DC detect these patterns and not call

      /host=somename/server=*

      , instead adding a step to read the server child names from /host=somename and then call /host=somename/server=a, /host=somename/server=b, etc.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              bstansbe@redhat.com Brian Stansberry
              Reporter:
              bstansbe@redhat.com Brian Stansberry
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: