[OPENAM-10127] SessionMonitoringStore should only be instantiated when monitoring is enabled - ForgeRock JIRA

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 13.0.0, 13.5.0, 14.1.1
Fix Version/s: 6.0.0.7, 6.5.1, 6.5.0.2, 6.0.1, 7.0.0
Component/s: monitoring, performance
Labels:
- EDISON

Target Version/s:

6.5.0, 6.0.0.7, 6.5.0.2
Rank:
1|hzwf9z:

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:

6.0.0.7, 6.5.0.2
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.