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

Memory leak in Amster Web Agent Administration

    Details

    • Type: Bug
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 5.5.1
    • Fix Version/s: None
    • Component/s: Amster
    • Labels:
    • Support Ticket IDs:

      Description

      Bug description

      Continually creating and deleting Web Agents via Amster  exhausts heap memory leading to a 502 Bad Gateway error.

       

      How to reproduce the issue

      Build:

       AM 5.0.0, Tomcat 8, Java 8, 2Gb Max heap

              patch with OPENAM-11154,OPENAM-5542OPENAM-11770OPENAM-11604

       DS 5.0.0 separate external config and user stores

              index-entry-limit > 1500, ds-rlim-size-limit > 1500

      Test:

      Via Amster scripts, create 1500 Web Agents then delete them. Repeat 10 times.

      Expected behaviour
      Script will run continuously.
      Current behaviour
      Heap utilisation progressively increases leading to high GC. Eventually Amster request times out after 10 seconds reporting 500 Bad gateway. 

      Work around

      Restart container before heap is exhausted.

      Code analysis

      Snapshots of heap-dump reports attached.

        Attachments

        1. AmsterAgentsLeak.png
          AmsterAgentsLeak.png
          789 kB
        2. dominatorTree.png
          dominatorTree.png
          172 kB
        3. leakSuspects.png
          leakSuspects.png
          131 kB

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tim.chandler Tim Chandler
            • Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated: