Stuart,

We are using undertow websocket library for passing back and forth serialized JSON messages using Websockets.sendText method

On the client side in Chrome we are noticing that that instead of 1 message we are receiving 2 where the first one is truncated at some 323,821 B and the second message is of 148,583 but malformed (its text but its garbled) and therefore not a JSON even if its concatenated with the first message

We are converting protocol buffers to JSON on the server side and can't point the finger at that code as it had worked for even bigger JSON messages.

To investigate this further I need help ruling out any message size or frame size limitation on undertow that could cause this. Any pointers here would be helpful.

Robin