[jetty-users] Websocket usage: Custom close codes not being retrieved by

[Chris Schmidt <CSchmidt@xxxxxxxxxxxxx>]

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