search

koush / AndroidAsync

Asynchronous socket, http(s) (client+server) and websocket library for android. Based on nio, not threads.
Other
7.52k stars 1.56k forks source link

Socket.io losing messages after TCP Retransmission #143

Open ctrox opened 10 years ago

ctrox commented 10 years ago

I'm running into a very weird issue that happens in about 1/10 connections. The server is emitting messages to the android client and at some point the android client stops receiving anything and no callbacks are triggered. The socket.io server isn't reporting any errors and heartbeats with the android client also continue. I used tcpdump on the socket.io server to see what is going on: wireshark The 188 IP is the server and the 194 is the android device. The android client received all the messages before the retransmission. All the websocket messages after that weren't received even though they were acknowledged. It seems like the socket.io client isn't aware of that retransmission and just discards the messages after that.

ArielSaldana commented 10 years ago

Did you ever figure out the issue?

ctrox commented 10 years ago

Sadly I have not. But as AndroidAsync doesn't look like it will ever support socket.io 1.0 I will switch to another library.