GSAInvalidatorService's Invalidate Cache Call Causes All Instances in Both Staging and Production to Invalidate Cache
Last updated on MAY 17, 2016
Applies to:Oracle Commerce Platform - Version 220.127.116.11 and later
Information in this document applies to any platform.
There are two separate CA targets: Staging and Production. Each of them has a number of deployment agent instances. In the custom code running on CA JVM, the GSAInvalidatorService.invalidate() method is called as follows:
Above call is expected to invalidate cache in all the agent instances in in one deployment target such as Staging. However such call will also trigger invalidating cache of all deployment agent instances in another deployment target such as Production target along with those in the expected target.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms