Designer-Gateway connection unstable

Ignition
1

My customer let me program Ignition from PC_client that I reach through RDP. PC_client’s Designer connects to the Ignition Gateway on PC_server: what I’m experiencing is a very unstable connection - disconnections happen every 2-3 minutes and working is almost impossible. My customer says they have no networking problem, but I’ve never experienced such an awful working experience in 10 years Ignition projects!

In the designer console I find the following messages when it disconnects:

09:10:30.798 [AWT-EventQueue-0] WARN com.inductiveautomation.ignition.client.gateway_interface.GatewayConnectionManager - Connection to Gateway lost, due to exception.
com.inductiveautomation.ignition.client.gateway_interface.GatewayException: Address already in use: no further information

09:10:30.868 [AWT-EventQueue-0] ERROR tags.manager - Error retrieving tag providers.
com.inductiveautomation.ignition.client.gateway_interface.GatewayException: Address already in use: no further information

Any suggestion?

Thanks in advance, regards

2

Looks like a duplicate IP on the network to me.

3

That is also my suspect: waiting for customer’s research about that.

Thanks

4

There have been past problems with RDP and designers, tracked to a java problem IIRC. But I haven't seen any lately--I think this was fixed.

What version is this?

5

Hi @pturmel, it’s 8.1.37.

Thanks, regards

6

Are there any errors in the gateway's logs?

Agree with the general consensus. The way client/designer <-> gateway RPC works requires the gateway to respond to an incoming HTTP request from the client/designer, at a pretty constant rate.

It might just be legitimate port exhaustion, if the sockets are being kept alive too long/there are too many incoming requests, though I would expect that to manifest as a different error.

7

Hi @paul-griffith , in the gateway log I find the same entries I find in the Designer console, which I post in this topic start.

Thanks, regards

8

I was mostly wondering if there was any more detail/stacktrace, which might help identify the nature of the problem.