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

Configuration objects not cleaned up as part of realm deletion

    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
    • Needs backport:
      Yes
    • Verified Version/s:
    • Needs QA verification:
      Yes
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      Bug description

      In case of AM's functional tests, new realms and configurations are created and deleted quite regularly during AM's lifetime.
      Especially when many different realms are removed, caches inside CachedSMSEntry and ServiceConfigImpl can contain lots and lots of out-of-date configuration objects. For example running the smoke tests left about 19k objects in CachedSMSEntry#smsEntries and ~13k ServiceConfigImpl instances. The leak is not limited to ServiceConfigImpl instances, however ServiceConfigImpl was the most severe cause, hence this issue only focuses on that one as a quick and easy win.

      How to reproduce the issue

      Run functional tests and look at the relevant cache objects on the heap.

      Expected behaviour

      config objects relating to deleted realms shouldn't stay around.

      Current behaviour

      Several thousand objects stay on heap.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: