000012885 - AxM - eserver cache flush event

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000012885
Applies ToRSA Access Manager 6.1
IssueHow to determine if cache flush event occurred.
How to determine if cache flush occurred.
ResolutionWhen the user is saved the cache will get flushed via DataUpdateEvent and DataUpdateListener.

Below are the console logs that will get generated on Eserver when the DEBUG facility is enabled.

11:53:01:933 [*] [QueueDispatcher] - refreshServerPool: AuthServerPool[ 10.30.95.28:5615:anon:_NO_AS_CLASS_:]
11:53:01:933 [*] [QueueDispatcher] - ======================CACHE FLUSH: START===============================
11:53:01:933 [*] [QueueDispatcher] - AuthServerConnection: started command . Now have 1 active commands
11:53:01:933 [*] [QueueDispatcher] - SEND MSG: DATA_MSG
11:53:01:949 [*] [MuxStreamReader-3] - MSG: DATA_MSG
11:53:01:949 [*] [QueueDispatcher] - Removing MuxStreamBundle
11:53:01:949 [*] [QueueDispatcher] - AuthServerConnection: command finished. Now have 0 active commands.
11:53:01:949 [*] [QueueDispatcher] -   Request count: 3, Avg. delay: 5.3333335 (this 16.0)
11:53:01:949 [*] [QueueDispatcher] - Cache Flushed successfully for the server:-10.30.95.28:5615
11:53:01:949 [*] [QueueDispatcher] - ======================CACHE FLUSH: END===============================
Legacy Article IDa61146

Attachments

    Outcomes