000024308 - Protected URL Caching

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 Number000024308
Applies ToRSA ClearTrust 5.5.3
IssueAserver performance is degraded when the protected URL cache is flushed.  Requests may queue on the server and cause an increase in the number of active threads. 
CauseIn hotfix 5.5.3.104 a new parameter 'cleartrust.aserver.cache.allow_protected_url_cache_flush' was introduced that allowed the protected URL cache to be flushed when granular updates are disabled.  When the cache is being updated the aserver cannot process any authorization requests.
ResolutionThis issue has been resolved in hotfix 5.5.3.128.  Contact RSA Customer Support and request this hotfix or the latest cumulative hotfix for you platform.  To prevent the delay when reloading the protected URL cache, hotfix 5.5.3.128 causes a temporary cache to be populated when the reload takes place, and the original cache remains until the temporary cache is complete. At this point, the protected URL cache is removed and replaced by the created temporary cache, which is then removed. This means that the protected URL cache is available all the time, the original is available while the new one is built, and once the new cache is built it is moved to the protected URL cache.
WorkaroundApplied Hotfix 5.5.3.104
Applied Hotfix 5.5.3.128
Legacy Article IDa35556

Attachments

    Outcomes