Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-12257

SMS listeners are not processed in the order they have been registered

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.0
    • Fix Version/s: 6.0.0, 14.1.2, 5.5.2
    • Component/s: sms
    • Labels:
      None
    • Target Version/s:
    • Needs backport:
      Yes
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      The notification listeners registered in various places within the SMS API do not always retain the order in which they have been registered, hence it is possible that sms-internal state updating listeners are invoked later than sms-user listeners meaning that those services may fail to pick up the actual changes the listeners were invoked about.

      How to reproduce the issue

      no clear reproduction steps, just randomly failing functional tests, like BlacklistingAuthSessions and TestAuthModuleInChain.

      Expected behaviour

      The listeners are always invoked in the order they've been registered.

      Current behaviour

      The listeners are invoked in random order.

        Attachments

          Activity

            People

            • Assignee:
              peter.major Peter Major [X] (Inactive)
              Reporter:
              peter.major Peter Major [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: