Do you have a test client/server that can replicate this? I only ask as the websocket TestClient [1] and TestServer [2] in jetty-8 does not appear exhibit this behavior.
[1] http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/tree/jetty-websocket/src/test/java/org/eclipse/jetty/websocket/TestClient.java?h=jetty-8 [2] http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/tree/jetty-websocket/src/test/java/org/eclipse/jetty/websocket/TestServer.java?h=jetty-8 -- Joakim Erdfelt <[email protected]> www.webtide.com Developer advice, services and support from the Jetty & CometD experts. On Tue, Aug 28, 2012 at 9:26 AM, Chris Schmidt <[email protected]>wrote: > Hello, > > I have a server and client implementation using the Jetty websocket > implementation (8.1.4 and 8.1.5). In one scenario the server will send a > certain amount of data and then close the connection using a custom close > code and message. The client doesn't seem to always get the custom close > code however. When run on the same machine, the custom close code is always > received. Over a network the most common close code retrieved is > 1006/Closed. Looking through the frames, I see the custom close message > coming into the client, but it seems to be within the same byte array as > the last text message. > > I'm unsure if this is a defect with Jetty itself. It seems to be, but > there may be something that needs to be done on the server side to ensure > that the close frame is sent in time for the client to process before the > connection closes. I've looked through Bugzilla and the mailing list but > haven't seen any mention of this. Anyone have pointers where I can dig into > this problem further? > > Thanks, > > Chris Schmidt > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
