[undertow-dev] We are noticing broken websocket messages

Stuart Douglas sdouglas at redhat.com
Tue Mar 22 18:30:34 EDT 2016


Their is no internal limitation in Undertow. Do you have a simple
reproducer I can look at?

Stuart

On Wed, Mar 23, 2016 at 2:52 AM, Robin Anil <robin.anil at gmail.com> wrote:
> 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


More information about the undertow-dev mailing list