Binary Message Too Large in Ignition Designer

Ignition
,
1

Hey everyone,

Our team recently upgraded to Ignition 8.3.1. Overall, our upgrade process was pretty smooth. This is our “main” Ignition gateway, and we have almost 10 other Ignition gateways that are incoming connections to this main. The connections were not really affected by the upgrade.

We do see one issue now that we have not seen before. On our main gateway, we also have it set up where it can view the other gateway’s default and system tag browser.

I get this error when I open one of the folders from a different tag browser:

11:54:52.899 [WebSocket@1841252200-49] ERROR com.inductiveautomation.ignition.client.gateway_interface.GatewayConnectionManager -- WebSocket error
org.eclipse.jetty.websocket.api.exceptions.MessageTooLargeException: Binary message too large: 2,113,509 > 2,097,152

In the same tag browser, I can open smaller folder that has less tags and I do not see this issue. I think I understand the error of there being too much data and agree this folder has a lot of data (several dataset tags), I just do not recall experiencing this issue before upgrading.

Does anyone have thoughts on this or does anyone know of a setting that can be changed to allow for larger messages? I can provide more information if it will help. Thank you all so much!

2

This is an issue we're tracking internally - some "under the hood" changes caused this issue to start occurring in 8.3 and we're going to make some further changes to resolve it in the future.

In the meantime, you can add a system property via the ignition.conf file that sets a larger size, in kB, for the ignition.designer.websocketMaxBinaryMessageSize property.

The default is 2048.

So all together you should end up adding a line like:
wrapper.java.additional.9=-Dignition.designer.websocketMaxBinaryMessageSize=4096

3 Likes