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

Connection leak in policy codebase

    XMLWordPrintable

Details

    • Rank:
      1|hzr3gv:
    • AM Sustaining Sprint 19
    • 0
    • Future
    • None

    Description

      Steps to reproduce:

      • create 2 or more policies in a new deployment
      • try to export them using ssoadm list-xacml

      Alternatively:

      • set up OpenAM with external config store
      • Create 1 policy
      • Save it and refresh the page 10+ times

      The problem seems to be that the SearchResultIterator#hasNext must be called to ensure that the underlying connection gets closed correctly. In DataStore#getPrivilege however the hasNext is only called once, and this means that the underlying connection is never actually closed/returned to the connection pool.

      Attachments

        Issue Links

          Activity

            People

              peter.major Peter Major [X] (Inactive)
              joe.starling Joe Starling
              Filip Kubáň [X] Filip Kubáň [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0h
                  0h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 5h
                  5h