High CPU usage observed if Gateway peering objects do not use unique ports

Problem

Steps 14-18 of the IBM API Connect documentation for Configuring DataPower API Gateway states users are required to use unique ports for the Local Port and Monitor Port defined in the different Gateway peering objects.

The expected behavior is when multiple Gateway peering objects are listening on the same port, there is a port conflict and one of the objects is down.

In these circumstances, users might see warnings and errors in the logs like:

1:03:19 PM apigw warning 3168 0x80e0085f gateway-peering (examplegatewaypeering): Detected a restart of the gateway peering server process that uses port 16480.
1:03:19 PM mgmt error 3168 0x810006ca gateway-peering (examplegatewaypeering): The configuration defines a port '16480' that is already in use.
1:03:19 PM apigw warning 3168 0x80e00860 gateway-peering (examplegatewaypeering): Detected a restart of the gateway peering monitor process that uses port 26480.
1:03:19 PM mgmt error 3168 0x810006ca gateway-peering (examplegatewaypeering): The configuration defines a port '26480' that is already in use.

Configuring multiple Gateway Peering objects to listen on the same ports when initially setting up of the Gateway peering manager, might result in the Gateway peering objects coming up and appearing to be listening on the same port.

In these circumstances users might see increased CPU usage on the DataPower and no evidence of errors from the misconfiguration.