tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niki Dokovski <nick...@gmail.com>
Subject Re: websocket client doesn't exit
Date Tue, 14 May 2013 13:55:56 GMT
Hi,
I found that when the NIO connector is used the problem is gone. With
protocol="org.apache.coyote.http11.Http11NioProtocol" in server.xml the
example is working just fine.

The wrong content of inputBuffer in WsFrameBase causes the observed
behavior and I haven't tracked it further to the default connector in
tomcat 8.

Best Regards
Nikolai


On Tue, May 14, 2013 at 1:40 PM, Niki Dokovski <nickytd@gmail.com> wrote:

> Hello,
> here is a small example based on JSR 356 defined APIs and implementation
> in tomcat 8 resulting in non exiting websocket client request. There is
> nothing special on both endpoints: On @ServerEndpoint there is simple
> OnMessage processing and on client side there is PongMessage handler. The
> client opens connection and sends ping message looking for the pong return.
> After executing 3,4 times the client (it is standalone client) hangs in
> constant executing of WsWebSocketContainer.processResponse ..
>
> where the buffer from which is read contains the same message of "The
> client frame set the reserved bits to [4] which was not supported by this
> endpoint"
>
> This happens on connectToServer call.
>
> Here I attach the war and client code which reproduce the problem. The JDK
> is Orcl JDK1.7_21.
>
> Could you please take a look at it and comment the observed behavior?
> Best regards
> Nikolai
>
> PS. I'm still digging into the implementation...
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message