<div dir="ltr">Sorry for not getting back because I didn't have a repro case. This issue happened last night and I was noticing that it was because the per-message size was in the 300K to 500K range. <div><br></div><div>So I tried to reduce our payload our issue went away. Digging in I noticed that the moment I disable PerMessageDeflateHandshake() extension the error goes away even at the large batch size. So this is what I have as an repro so far</div><div><br></div><div><br></div><div>Robin</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Mar 22, 2016 at 5:30 PM Stuart Douglas <<a href="mailto:sdouglas@redhat.com">sdouglas@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Their is no internal limitation in Undertow. Do you have a simple<br>
reproducer I can look at?<br>
<br>
Stuart<br>
<br>
On Wed, Mar 23, 2016 at 2:52 AM, Robin Anil <<a href="mailto:robin.anil@gmail.com" target="_blank">robin.anil@gmail.com</a>> wrote:<br>
> Stuart,<br>
><br>
> We are using undertow websocket library for passing back and forth<br>
> serialized JSON messages using Websockets.sendText method<br>
><br>
> On the client side in Chrome we are noticing that that instead of 1 message<br>
> we are receiving 2 where the first one is truncated at some 323,821 B and<br>
> the second message is of 148,583 but malformed (its text but its garbled)<br>
> and therefore not a JSON even if its concatenated with the first message<br>
><br>
> We are converting protocol buffers to JSON on the server side and can't<br>
> point the finger at that code as it had worked for even bigger JSON<br>
> messages.<br>
><br>
> To investigate this further I need help ruling out any message size or frame<br>
> size limitation on undertow that could cause this. Any pointers here would<br>
> be helpful.<br>
><br>
> Robin<br>
</blockquote></div></div>