GENERAL_PROTOCOL_EXCEPTION between two 8.1.27 gateways connected via GAN and RTP

Ignition
1

Hellow all, we had the same "GENERAL_PROTOCOL_EXCEPTION" error couple of months before between our gateways connected via GAN but with ignition support help after numerous trails and calls were able to identify the source to be voice module. Since we don't use that module we uninstalled the module and things started work again.

Now we added another gateway to the GAN and below is the setup.
Gateway1: We have 8.1.27 gateway with a dataset memory tag
Gateway2: We have another 8.1.27 gateway with Outgoing GAN into above gateway and RTP setup.

Error on Gateway2 status page:
com.inductiveautomation.metro.api.ex.RemoteException: Exception occurred on remote machine, message id='18993', error code=GENERAL_PROTOCOL_EXCEPTION [100]
at com.inductiveautomation.metro.impl.protocol.handler.AckErrorHandler.handleMessage(AckErrorHandler.java:76)
at com.inductiveautomation.metro.impl.protocol.websocket.WebSocketConnection$RunSend.run(WebSocketConnection.java:1879)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

Error on Gateway1 status page:
com.inductiveautomation.metro.api.ex.RemoteException: Exception occurred on remote machine, message id='28203', error code=GENERAL_PROTOCOL_EXCEPTION [100]
at com.inductiveautomation.metro.impl.protocol.handler.AckErrorHandler.handleMessage(AckErrorHandler.java:76)
at com.inductiveautomation.metro.impl.protocol.websocket.MetroWebSocket.onMessage(MetroWebSocket.java:378)
at org.eclipse.jetty.websocket.core.internal.messages.DispatchedMessageSink.lambda$accept$0(DispatchedMessageSink.java:122)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078)
at java.base/java.lang.Thread.run(Unknown Source)

Appreciate the help

2

Is the dataset memory tag very large? You might be exceeding the GAN's message size limits.

3

Seems like the issue is 8.1 present since 2021 :blush:

One of our team members was able to find this notes from then support analysis : “Seems that the problem comes when referencing the tag's own LastChange property. Since technically the tag's LastChange gets updated every time that binding gets evaluated, it leads to an infinite loop and will cause issues with the rest of the project.” And the issue is resolved now by identifying the tag expression that is using .LastChange and fixing that. No more errors and now we are able to save the project with out any issues.