Idle timeout expired filling logs 2x/min

In 8.1.43:
Yesterday afternoon I started to see this error in my logs:

handleException /system/gateway java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms

I get the error 1 or 2x / min.

It does not seem to be related to the launch of any client. I can't seem to find much information about this.

My line-side display clinent are set to poll at 5 sec intervals. All my gateway network settings are default. I tried changing Websocket Idle timeout to 60,000 but no change.

What specifically is timing out to trigger this message?

Can anyone suggest where I might start looking for the cause?

It seems to only occur when I have the Designer open.

Closing the loop in this:

I reached out to tech support:

This means that some sort of a connection to the Gateway has time out because the client was idle too long. The message is saying that the connection sat idle for about ~30 seconds so the Gateway closed it which caused that error to get logged. I don't believe that this error is an actual issue as the Gateway is only saying that some web socket connection to the Gateway is idle.

This message is very vague and generic timeout message. This message could be talking about a designer connection, vision client connection, or perspective session being idle.

the message you're seeing in the logs is likely tied to your Designer or Vision Client connection. Based on what you've described, I suspect the issue is being triggered by the unstable or limited bandwidth between your client and the server with the VPN.

Here’s what I think may be happening, when the connection is first established, everything functions normally. However, if there's a brief network drop or an issue, the original WebSocket connection may be silently broken or timed out. While a new web socket connection gets established when the network recovers, the server might still have the previous connection hanging in a half-open state, which eventually times out and logs the message you're seeing. You can try increasing the timeout of the designer launcher and see if that helps out.