The fun part of dealing with websockets at this point in time is getting
both browser and server to speak the same version. The protocol has
been under heavy development for some time and the adoption rates vary
on both end points. As of grizzly 1.9.37 ( unreleased ), I've fixed it
so that it can detect which version the browser speaks. Using my script
(
http://antwerkz.com/glassfish-ose-3-1-is-out-with-websocket-support-included/),
you can update GlassFish to use grizzly 1.9.37-SNAPSHOT. That should at
least rule out protocol version mismatches. That configuration of
GlassFish (using 1.9.37-SNAPSHOT) has not undergone QA here so it would
an unsupported (officially) configuration but will hopefully address
this issue for you.
On 7/29/11 12:44 AM, forums_at_java.net wrote:
> words , say in case of the chat application User-User
> interaction works fine ,