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

SessionMonitoringStore should only be instantiated when monitoring is enabled

    Details

    • Sprint:
      AM Sustaining Sprint 41, AM Sustaining Sprint 42, AM Sustaining Sprint 43, AM Sustaining Sprint 44, AM Sustaining Sprint 45, AM Sustaining Sprint 46, AM Sustaining Sprint 47, AM Sustaining Sprint 48, AM Sustaining Sprint 49, AM Sustaining Sprint 50, AM Sustaining Sprint 51, AM Sustaining Sprint 52, AM Sustaining Sprint 53, AM Sustaining Sprint 54, AM Sustaining Sprint 55, AM Sustaining Sprint 56, AM Sustaining Sprint 57
    • Story Points:
      3
    • Needs backport:
      Yes
    • Support Ticket IDs:
    • Verified Version/s:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      Yes and I used the same an in the description

      Description

      When using AppDynamics to analyse OpenAM's performance during authentication it turns out the one of the most expensive methods is the construction of SessionMonitoringStore, see attached screenshot from AppDynamics.

      As it seems the counters are only leveraged by OpenAM monitoring , the objects should only be initiated when OpenAM monitoring is enabled. However this is not the case by default.

        Attachments

          Activity

            People

            • Assignee:
              markdr Mark de Reeper
              Reporter:
              bthalmayr Bernhard Thalmayr
            • Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: