pdweb.sescache component
The pdweb.sescache component
gathers statistics about the WebSEAL
session cache. This component gathers the following activity information:
- hit
- The number of requests where a cache entry for a user was referenced successfully. That is, the number of requests that resulted in a session cache hit.
- miss
- The number of requests that missed a session cache hit.
- add
- The number of cache entries that was added to the session cache.
- del
- The number of cache entries that was deleted from the session cache.
- inactive
- The number of times where a cache entry hit the inactivity timeout.
- lifetime
- The number of times where a cache entry hit the lifetime timeout.
- LRU expired
- The
number of times that a
least recently used
cache entry was deleted from the session cache to make room for a new cache entry.
The following example shows the output from
a stats get command
for the pdweb.sescache component:
pdadmin sec_master> server task default-webseald-instance stats get pdweb.sescache
hit : 225
miss : 75
add : 375
del : 150
inactive : 60
lifetime : 15
LRU expired : 75In the previous release, the pdweb.sescache
component contained
activity that was associated with callback certificates and user session
mappings. These statistics are now managed by the following components:
- pdweb.certcallbackcache
- This cache stores the SSL IDs of sessions that require certificate validation when a user is stepping up. The reported information has the same categories as pdweb.sescache. These activities are internal.
- pdweb.usersessidcache
- This cache stores a mapping of users to their sessions. The reported information has the same categories as pdweb.sescache. These activities are internal.
Therefore, the first time
that you gather statistics for the pdweb.sescache
component and compare it to your last report, the figures might appear
to be wrong. To set a new baseline, add the statistics from the following
components and then compare them to your previous baseline (last pdweb.sescache
report):
- pdweb.sescache
- pdweb.certcallbackcache
- pdweb.usersessidcache
The output against the pdweb.sescache component
must be your new baseline.