000022637 - How to determine if a full cache flush event was initiated in RSA ClearTrust

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

Article Content

Article Number000022637
Applies ToRSA ClearTrust 5.0.1 Authorization Server (AServer)
IssueHow to determine if a full cache flush event was initiated in RSA ClearTrust
RSA ClearTrust Authorization Server (AServer) shows increased load as the result of cache flush events initiated by Administrative API or Entitlements Manager (Admin GUI)
RSA ClearTrust Agents return the following error message:

2003-06-17 11:03:27:655 PDT,Client IP Address =,Client Port = 3087,Result Code = 0,Request not serviced,Result Reason = Auth server busy
In the RSA ClearTrust Authorization Server (AServer) debug output, the following lines indicate that a full cache flush event has occurred, and that the URI cache is being reloaded. The Begin and Finished lines of the URI cache indicate the time required to reload the URL cache. The URL cache is normally never reloaded except during a full cache flush and during server startup.

2006/02/08 16:07:26:479 [*] [MUX_Request_Thread_14 (sirrus.util.data.DataUpdateEventDispatcher.fireDataUpdateEvent)] - Firing "CLEAR" event.

2006/02/08 16:07:26:479 [*] [Data_Update_Event_Dispatcher (sirrus.authserver.ProtectedURLCache.performPreload)] - Begin loading URI cache at Wed Feb 08 16:07:26 CST 2006

2006/02/08 16:07:27:681 [*] [Data_Update_Event_Dispatcher (sirrus.authserver.ProtectedURLCache.performPreload)] - Finished loading URI cache, server count is 16
RSA ClearTrust Authorization Server (AServer) log shows the following entry:

2006-02-13 11:13:42:453 PST, conn=0, op=8, msgid=2302, ip=, uname=Administrator, msg="Flush cache", result=0, etime=109ms
ResolutionA full flush cache event can have serious performance impact on the RSA ClearTrust Authorization Server (AServer). The proxy.flushcache command was deprecated as of hot fix This hot fix introduced the concept of granular cache flush during save() operations. It is recommended that customers upgrade to hot fix or later and avoid the use of the manual cache flush command.
WorkaroundThe RSA ClearTrust Administrative API command proxy.flushcache() was called to ensure that changes to the Entitlements Server are flushed from the AServer cache
Legacy Article IDa29660