search

mrniko / netty-socketio

Socket.IO server implemented on Java. Realtime java framework
Apache License 2.0
6.82k stars 1.65k forks source link

chrome and ie9 dont work as good as ff #32

Closed chembohuang closed 11 years ago

chembohuang commented 11 years ago

I've run the example, find out that chrome and ie9 dont work as good as ff. Sometimes the connection takes two times to build and sometimes it couldn't be made and throw the exception as follows:

148 [main] INFO com.corundumstudio.socketio.SocketIOServer - SocketIO server started at port: 9092 5323 [New I/O worker #7] ERROR com.corundumstudio.socketio.handler.PacketHandler - Exception occurs java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:237) at sun.nio.ch.IOUtil.read(IOUtil.java:204) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:59) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:471) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:332) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:35) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

am in missing sth. or a bug or what? pls give some help. thanks in advance.

mrniko commented 11 years ago

I just updated netty-socketio-demo decription. You need to host demo *.html pages somewhere on web server. Don't lunch it locally like usual file it doesn't work.

chembohuang commented 11 years ago

in fact, i did. i host the static files on apache2.2.

chembohuang commented 11 years ago

FYI: console of the chrome: http://s3.sinaimg.cn/middle/6ac6cf68gcfd700f1a662&690

mrniko commented 11 years ago

Could you try it again with latest update from git? I noticed a websocket handshake error in your screenshot, I have fixed it in last commit. Can't reproduce your problems with NamespaceChatLuncher example. I lunched it locally and all works fine.

chembohuang commented 11 years ago

yes, the latest version works. but there are still some problems under the safari on ipad, sometimes it disconnects automatically, sometimes it couldnt get the message as fast as other browsers did.

mrniko commented 11 years ago

Does this problem reproduces on node socket.io server? Because i don't have an ipad, can't check it.