API GW is randomly sending request to non standard port in 'Route via HTTP to' assertion

Products

• CA API Gateway

Issue/Introduction

The API GW is randomly sending a request to non standard port via the 'Route via HTTP to' assertion. 

The API GW is sending a request to port 7220 instead of 443. The URL in the assertion is filled with string ${apiLocation} coming from API Portal and does not contain port (e.g. 'https://<GATEWAY>/1.1/order'). 

Port 7220 is defined as a CWP on same API GW but for other API GW services.
For example - from one client, a total of 196,000 requests were sent during the last batch load (90 minutes). There were 30 timeout errors like below:

"Problem routing to https://<GATEWAY>/notification/1.1/order. Error msg: Unable to obtain HTTP response from https://<GATEWAY>/notification/1.1/order: Connect to <GATEWAY>.internal:7220 timed out"

After our customer upgraded to version 11.1, the issue still persists.

While the workaround mentioned in KB Occasional routing failures due to connections to incorrect ports (using an explicit port) is appreciated, it does require manual steps from the clients and carries a risk of human error. It may not be the best long-term solution.

Environment

API Gateway 11.1

Resolution

This issue is resolved in the Gateway 11.2 which has a new httpclient library.