API Gateway restart is failing for one node

Hi,

We are seeing issue with API Gateway restart. One of the nodes is not connecting. The following exception is seen in the logs.
[ISC.0064.0027C] 880 Requests are waiting (for an available connection) to be forwarded across Registration Port 7333 to an Internal Integration Server

Why are requests waiting (for an available connection) to be forwarded across Registration Port to Internal Server (Integration Server)?

Thanks and Regards,
Rup

This issue could be due to the number of connections maintained between Enterprise
Gateway Server and the Internal Server, by default it is 5. Try increasing the Maximum Connections in Security > Ports > Edit Internal Server Configuration

Note: For best performance, set the Max Connections setting on the listener to be slightly less than the Maximum Threads of the Server Threadpool setting on the Settings > Resources page. If you have more than one listener defined on the Internal Server, the sum of their Max Connection settings should be slightly less than the Maximum Threads of the Server Threadpool setting. Do not set Max Connections to be equal to the Internal Server’s threadpool. Instead, reserve enough threads to handle the execution of scheduled services, triggers, and users that connect directly to the Internal Server.

Additionally you can also try to set the following watt settings watt.server.rg.internalregistration.timeout property to 180 and watt.server.rg.gateway.pinginterval to 60 in the internal gateway and DMZ gateway respectively