You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Bob DeRemer <bo...@thingworx.com> on 2013/08/16 19:08:51 UTC
Tomcat 7.0.42 closing websocket without any error receiving
WebSocket ContinuationFrames
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?
Thanks,
Bob DeRemer
Senior Director, Architecture and Development
[Description: Description: Description: Description: cid:image001.png@01CBE3DE.51A12030]
http://www.thingworx.com<http://www.thingworx.com/>
Skype: bob.deremer.thingworx
O: 610.594.6200 x812
M: 717.881.3986
RE: Tomcat 7.0.42 closing websocket without any error receiving
WebSocket ContinuationFrames
Posted by Bob DeRemer <bo...@thingworx.com>.
> -----Original Message-----
> From: Mark Thomas [mailto:markt@apache.org]
> Sent: Friday, August 16, 2013 3:18 PM
> To: Tomcat Users List
> Subject: Re: Tomcat 7.0.42 closing websocket without any error receiving
> WebSocket ContinuationFrames
>
> On 16/08/2013 20:01, Bob DeRemer wrote:
> >
> >
> >> -----Original Message-----
> >> From: Mark Thomas [mailto:markt@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.
Sounds good, thx!
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7.0.42 closing websocket without any error receiving WebSocket
ContinuationFrames
Posted by Mark Thomas <ma...@apache.org>.
On 16/08/2013 20:01, Bob DeRemer wrote:
>
>
>> -----Original Message-----
>> From: Mark Thomas [mailto:markt@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Tomcat 7.0.42 closing websocket without any error receiving
WebSocket ContinuationFrames
Posted by Bob DeRemer <bo...@thingworx.com>.
> -----Original Message-----
> From: Mark Thomas [mailto:markt@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?
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 7.0.42 closing websocket without any error receiving WebSocket
ContinuationFrames
Posted by Mark Thomas <ma...@apache.org>.
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.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org