dev@grizzly.java.net

Re: Problem with WebSockets using Grizzly in latest Glassfish 3.1 and Chromium

From: Justin Lee <justin.d.lee_at_oracle.com>
Date: Mon, 28 Jun 2010 09:17:29 -0400

Yes, you'll notice the "detect closed sockets" issue is still open. I'm
getting there but haven't made it to that one yet. The header change,
however, was made by one of the other glassfish devs for some servlet
3.0 stuff. We're still debating whether or not that change was
correct. It doesn't seem to affect anything, though. The HTTP spec
does not mandate fixed values for those header messages and chrome
certainly doesn't mind the change in text. It broke a few unit tests
but so far that seems to be the largest impact.

On 6/28/10 5:11 AM, Ido Ran wrote:
> Hi,
> I'm back on getting WebSocket application up and running.
>
> First, the response from the server handshake has change
> HTTP/1.1 101 Web Socket Protocol Handshake into
> HTTP/1.1 101 Switching Protocols
>
> It's not that different but just to make sure it is right because in the
> trunk of grizzly it still saying the first one in prepare(Response) method.
>
> There is still problem with detection of closed sockets, they keep pile up
> in the server and no data can be broadcast because the application get stuck
> on the first send() method call. I have try/catch around it and there is no
> exception get thrown, just hanging as far as I can tell.
>
> I'll keep on trying but I'll be happy to get some help about how to use it.
>
> Thank you,
> Ido
>
>