Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internet Explorer 10 websocket error #51

Closed
borisvyle opened this issue Oct 1, 2013 · 6 comments
Closed

Internet Explorer 10 websocket error #51

borisvyle opened this issue Oct 1, 2013 · 6 comments
Labels

Comments

@borisvyle
Copy link

Hi,

I have this kind of problem with IE 10.
After 40 seconds of inactivity on my chat, I have on my IE Console :

SCRIPT12030: WebSocket Error: Network Error 12030, La connexion avec le serveur a été interrompue anormalement

And on my log in atmosphere :


2013-10-01 11:56:59,173 DEBUG o.a.nettosphere.BridgeRuntime - Exception
java.lang.UnsupportedOperationException: org.jboss.netty.handler.codec.http.websocketx.PongWebSocketFrame frame types not supported
        at org.atmosphere.nettosphere.BridgeRuntime.handleWebSocketFrame(BridgeRuntime.java:276) ~[nettosphere-2.0.0.jar:na]
        at org.atmosphere.nettosphere.BridgeRuntime.messageReceived(BridgeRuntime.java:232) ~[nettosphere-2.0.0.jar:na]
        at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:142) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:536) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) ~[netty-3.6.3.Final.jar:na]
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) ~

I don't know how I can manage this kind of PongWebSocketFrame.

I'm using ATMOSPHERE 2.0.1 and Nettosphere 2.0.0

Thanks

@jfarcand
Copy link
Member

jfarcand commented Oct 1, 2013

OK fixed in 2.0.1-SNAPSHOT. Try it and let me know I will cut a release. Merci!

@jfarcand jfarcand closed this as completed Oct 1, 2013
jfarcand added a commit that referenced this issue Oct 1, 2013
@borisvyle
Copy link
Author

Tested and It works perfectly !
Thanks

jfarcand added a commit that referenced this issue Oct 2, 2013
@jfarcand
Copy link
Member

jfarcand commented Oct 2, 2013

@borisvyle 2.0.1 released :-)

@dardok
Copy link

dardok commented Jun 6, 2014

Commented on commit 8856873, which I believe to be incorrect.

jfarcand added a commit that referenced this issue Jun 6, 2014
@jfarcand
Copy link
Member

jfarcand commented Jun 6, 2014

@dardok Fair enough, I've made it optional and configurable. Do you need a release? I will cut 2.2 in a week or so, but can backport the fix to 2.1.x

2.2.0-RC1 contains the fix.

@dardok
Copy link

dardok commented Jun 7, 2014

My nettosphere is under a third-party layer of which I have little control. I've backported into the specific version used, so I'm good. Glad master will have the appropriate fix, but perhaps the option should be called "enablePingForPong" or something else more descriptive? Thanks for making the default "false", though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants