On 16/08/2013 20:01, Bob DeRemer wrote: > > >> -----Original Message----- >> From: Mark Thomas [mailto:ma...@apache.org] >> Sent: Friday, August 16, 2013 1:40 PM >> To: Tomcat Users List >> Subject: Re: Tomcat 7.0.42 closing websocket without any error receiving >> WebSocket ContinuationFrames >> >> On 16/08/2013 18:08, Bob DeRemer wrote: >>> Hi Tomcat community, >>> >>> Has anyone had a large WS message sent as the response to an outbound >>> call? We have a scenario where the request causes a 300K WS message >>> to be sent back as the "response". The client is sending multiple WS >>> continuation frames and after a couple of frames are successfully >>> sent, Tomcat just closes the websocket connection. I the response >>> fits in a single frame, it's fine. >>> >>> Where can I look to try and troubleshoot this? >> >> My first stop would be something like Wireshark to check that what the >> client is >> sending is valid. >> >> If the input is valid then there isn't much logging in the Tomcat 7 >> non-JSR356 WebSocket implementation so I'd probably move on to remote >> debugging to see what is going on. >> > > Assuming the continuation frames are ok, what code in the non-jsr IMPL should > I set some breakpoints in?
I'd start with org.apache.catalina.websocket.WsFrame.nextFrame(...) You may need to go up or down the stack from there depending on where the problem lies. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
