Cache assertions functionality

Products

• CA API Gateway

Issue/Introduction

I want to know API Gateway cache function of both version of 10.1 CR03 and 11.0.

1. As for Look Up in Cache / Store to Cache assertions, do they use Exclusion Control when reading and updating cache?
2. Similar to (1). Is there any possibility of that these assertions could encounter deadlock.
3. Also, if there is the functional difference between the two versions, please provide the information on it.

Environment

Release : API Gateway 10.1, 11.0

Resolution

Here are the answers.

1. When reading and updating the cache; access is controlled by synchronization.
   • The synchronization is applied to each cache instance. 
2. The Cache assertion was productized in version 5.4, and is used frequently by our customers and other GW offerings such as the OTK. 
   • No defects currently exist, thus the assertion code is highly unlikely to contain a deadlock situation. Additionally the synchronization blocks are small and only single locks exits. 
3. No functional differences between version 10.1 and 11.0