Tactical Remote Cache Assertion - "Unable to store cached value: Could not get a resource from the pool"

Products

• CA API Gateway

Issue/Introduction

The tactical assertion 1.3.4 is not working and the following error is seen in the log file:

"ServerRemoteCacheStoreAssertion: 4: Unable to store cached value: Could not get a resource from the pool. Exception caught!"

A Redis cache server on Azure is used with this tactical assertion. There is no firewall in between the Gateway and Redis server and a successful connection can be established via telnet and OpenSSL.

 

Environment

Release : 10.0

Component : API GATEWAY

Resolution

This issue is caused by the "In Transit Encryption" feature which is not supported in the older assertions. The latest release of tactical remote cache assertion does support this feature.

There is a new option (check box) "TLS(AWS)" added in the assertion configuration. Enabling this option will support the "In Transit Encryption" feature for both AWS and Azure.