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

SumCTSSessions monitoring variable runs search over entire CTS suffix

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 12.0.0
    • Fix Version/s: None
    • Component/s: CTS, monitoring
    • Labels:
    • Sprint:
      AM Sustaining Sprint 23, AM Sustaining Sprint 24, AM Sustaining Sprint 25, AM Sustaining Sprint 27, AM Sustaining Sprint 28, AM Sustaining Sprint 29, AM Sustaining Sprint 30
    • Support Ticket IDs:

      Description

      To reproduce:

      1) Setup OpenAM
      2) Enable monitoring, e.g HTTP
      3) Fetch SumCTSSessions variable, e.g:

      http://openam.example.com:8082/ViewObjectRes//FORGEROCK_OPENAM_SESSION_MIB%3Aname%3Dorg.forgerock.openam.monitoring.session.CtsSessions 
      

      Result:

      OpenAM will run this query against CTS to get the result:

      Search Request: SearchRequest(name=ou=famrecords,ou=openam-session,ou=tokens,dc=openam,dc=forgerock,dc=org, scope=sub, dereferenceAliasesPolicy=never, sizeLimit=0, timeLimit=0, typesOnly=false, filter=(&(objectClass=frCoreToken)(&)), attributes=[coreTokenId], controls=[])
      Filter: (&(objectClass=frCoreToken)(&))
      Result: Result(resultCode=Success, matchedDN=, diagnosticMessage=, referrals=[], controls=[])
      
      [13/May/2016:17:53:17 -0400] SEARCH REQ conn=30 op=129713 msgID=129714 base="ou=famrecords,ou=openam-session,ou=tokens,dc=openam,dc=forgerock,dc=org" scope=wholeSubtree filter="(&(objectClass=frCoreToken)(&))" attrs="coreTokenId"
      

      This approach does not scale at all. In a system with many thousands of tokens the directory server will need to iterate over and return the token ID of every token.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 4h
                  4h
                  Remaining:
                  Remaining Estimate - 4h
                  4h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified