Policy manager returns 'Gateway Inactivity Session Timeout has been reached' for container Gateways when the replica set is more than one.

Products

• CA API Gateway

Issue/Introduction

The business is currently in the process of migrating from appliance gateways (10.1) to container gateways (11.1.1). The container gateway is working fine when replicatset=1 but when the parameter is increased to >1, the following message is observed when logging in to Policy Manager (PMTagger):

Gateway Inactivity Session Timeout has been reached

Environment

Container Gateway 11.1

Resolution

The DNS mapping from the load balancer was not correct. The DNS needed to be resolved to the correct AWS internal domain name as specified in the internal environment.