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!
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
EDIT:
Alternately, if you're getting this message too large error in the designer, then you need to close the designer and edit the application launch settings in the Designer Launcher.
In the 'Additional JVM Arguments', add a system property override:
-Dignition.designer.websocketMaxBinaryMessageSize=4096
7 Likes
So running into the same issue and this solution is not working for us on 8.3.2. Do you have any other suggestions?
edit: Looking at the logs I can see that even though we added that to the config the error still indicates in bytes that the limit is 2048. So for some reason its not updating properly.
Did you restart after modifying ignition.conf?
edit: also I would have thought this property needed to be set when launching the Designer and not in ignition.conf... but 
I did and before seeing your message I instead added it as a JVM argument and that resolved the issue. I was just coming back to update my post! Thank you though for suggesting the correct solution.
Edit: Just to clarify for other users that have this issue and come to this thread. What worked for me was going to manage for the application I want to launch in designer and adding this as a JVM argument: -Dignition.designer.websocketMaxBinaryMessageSize=4096
3 Likes
It depends on which side of the handshake the too large message is coming from. For the original poster, it was happening on the gateway side. It's the same system property either way, though. I'll update my first post to clarify.
1 Like