<html>
<head>

</head>
<body>
<div style="color: black;">
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black;">We don't see an exception. The
received data simply doesn't match the data sent.</p>
</div>
<div style="color: black;">
<p
style="color: black; font-size: 10pt; font-family: Arial, sans-serif; margin: 10pt 0;">On
October 9, 2015 8:39:38 AM peter royal &lt;peter.royal@pobox.com&gt; wrote:</p>
<blockquote type="cite" class="gmail_quote"
style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<p>On 2015-10-09 09:05, Greg Shrack wrote:</p>
<blockquote type="cite"
style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!--
html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">
<div id="yui_3_16_0_1_1444397807457_6087"
style="color: #000000; font-family: 'Helvetica Neue','Segoe UI',Helvetica,Arial,'Lucida Grande',sans-serif;">
<p id="yui_3_16_0_1_1444397807457_6086" class=""
style="font-size: 13px; margin: 0px; padding: 0px;"><span
style="font-size: 10.5pt;">I'm seeing an inconsistent problem where some
messages are corrupted. We're sending serialized objects over websockets,
and are seeing some corrupted messages with larger messages and sometimes
when sending more quickly.&nbsp;</span><span style="font-size: 14px;">We've
testing with a number of versions including undertow 1.1.8.Final, but was
seeing the same issue with newer versions as well.&nbsp; Wireshark appears
to show the corrupted data on the client side</span></p>
</div>
</div>
</blockquote>
<p>&nbsp;</p>
<p>Is it this stack trace?</p>
<p>&nbsp;</p>
<p><span>ava.io.IOException:
io.undertow.websockets.core.WebSocketFrameCorruptedException: UT002010:
Received continuation data frame outside </span><span
id="0.25815421529114246"
class="currentHitHighlight">fragment</span><span>ed message</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.WebSocketChannel.parseFrame(WebSocketChannel.java:184)
~[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.server.protocol.framed.AbstractFramedChannel.receive(AbstractFramedChannel.java:340)
~[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:38)
[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.AbstractReceiveListener.handleEvent(AbstractReceiveListener.java:33)
[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[xnio-api-3.3.1.Final.jar:3.3.1.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:775)
[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.server.protocol.framed.AbstractFramedChannel$FrameReadListener.handleEvent(AbstractFramedChannel.java:763)
[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
[xnio-api-3.3.1.Final.jar:3.3.1.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
[xnio-api-3.3.1.Final.jar:3.3.1.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:88)
[xnio-nio-3.3.1.Final.jar:3.3.1.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
org.xnio.nio.WorkerThread.run(WorkerThread.java:539)
[xnio-nio-3.3.1.Final.jar:3.3.1.Final]</span><br /><span>Caused by:
io.undertow.websockets.core.WebSocketFrameCorruptedException: UT002010:
Received continuation data frame outside </span><span
id="0.5534121757373214" class="highlight">fragment</span><span>ed
message</span><br /><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.protocol.version07.WebSocket07Channel$WebSocketFrameHeader.validateDataFrame(WebSocket07Channel.java:418)
~[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.protocol.version07.WebSocket07Channel$WebSocketFrameHeader.handle(WebSocket07Channel.java:267)
~[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at
io.undertow.websockets.core.WebSocketChannel.parseFrame(WebSocketChannel.java:174)
~[undertow-core-1.2.8.Final.jar:1.2.8.Final]</span><br
/><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ... 10 common frames
omitted</span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>I intermittently get the above with 1.2. I helped refactor the
websocket implementation in 1.3 and it should (hopefully) not exhibit that.
I haven't pushed it into my production applications yet though.</span></p>
<p>&nbsp;</p>
<p><span>Have you tested one of the 1.3 candidates?</span></p>
<p>&nbsp;</p>
<p><span>-pete</span></p>
<p>&nbsp;</p>
<div>
<div class="pre"
style="margin: 0; padding: 0; font-family: monospace"><span
class="sig">--&nbsp;<br /> (peter.royal|osi)@pobox.com - <a
href="http://fotap.org/~osi" target="_blank"
rel="noreferrer">http://fotap.org/~osi</a><br /> </span></div>
</div>
</blockquote>
</div>
</div>
</body>
</html>