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

still frequently reconnection in my first connection, wait on line...., my log is here #229

Closed
hpustudent opened this issue Oct 18, 2015 · 15 comments

Comments

@hpustudent
Copy link

my server is node.js+socket.io ,the version of socket.io is 1.x,the problem is stil alive,my app is about to on the line , is anyone know the other way to connect to socke.io server?

this is my log:
3

transport is always "polling"

can I contact to you with IM so that i can support you more infomation?

@hpustudent hpustudent changed the title still frequently reconnection in my first connection, I want to cry.... still frequently reconnection in my first connection, wait on line.... Oct 19, 2015
@hpustudent hpustudent changed the title still frequently reconnection in my first connection, wait on line.... still frequently reconnection in my first connection, wait on line...., my log is here Oct 19, 2015
@nkzawa
Copy link
Contributor

nkzawa commented Oct 20, 2015

Do you mean having the same problem before too? Can you post your code?
Regarding WebSocket connection, it can fail for many reasons. So I recommend to check whether bare WebSocket works fine or not.

@hpustudent
Copy link
Author

@nkzawa our app contains ios and android , the ios version works well and the socket.io module is supported by socket.io official, if it is possible , you can remote control my computer for solving the problem, here is my code , i will online to wait you thanks:

the next 3 method is from my SocketClient class
1
2
3

the method below is in SocketPost class
4

and i will call SocketPost.getNews(onGetNews.getPackageId(), null, null) with params to request the web server.

here is the log detail
log

@nkzawa
Copy link
Contributor

nkzawa commented Oct 20, 2015

Unfortunately, I can't help you like that. Your code looks OK. Do you know how we can reproduce the issue? Any other detailed logs?

@hpustudent
Copy link
Author

my android app runs on 300 mechines for testing,they always encounter the problem in any time.Our app will run on hundreds of thousands of machines, so we can not directly on the line before this problem can not be solved.
the more log details after previous:
log2
log3

@hpustudent
Copy link
Author

I just bought a server, I will build a test environment as soon as possible, and then tell you the account and password, in order to reproduce the bug。But I'm worried about that the test environment is only a device connection, this error will not reproduce。

@nkzawa
Copy link
Contributor

nkzawa commented Oct 20, 2015

Thanks for the logs, but still I have no idea.

Can you modify the source code of engine.io-client-java, and debug what kind of errors actually happen in the following methods?

https://github.com/socketio/engine.io-client-java/blob/master/src/main/java/io/socket/engineio/client/transports/PollingXHR.java#L250
https://github.com/socketio/engine.io-client-java/blob/master/src/main/java/io/socket/engineio/client/transports/WebSocket.java#L134

@hpustudent
Copy link
Author

123439

the other error is :

8

the more log:

213

@hpustudent
Copy link
Author

I already update the logs ,please see the post above.

@hpustudent
Copy link
Author

@nkzawa It seems the error is caused by okHttp, square/okhttp#1114

@nkzawa
Copy link
Contributor

nkzawa commented Oct 21, 2015

@hpustudent sorry for the delay. looks like so. Does android:vmSafeMode: true work for you?

@hpustudent
Copy link
Author

The problem is still alive,but why can't the websocket transport build? any solution

@nkzawa
Copy link
Contributor

nkzawa commented Oct 22, 2015

What version of socket.io-client-java do you use? Can you test with the latest version if you are using an old version, since they say okio was fixed on 1.6.0.

square/okhttp#1518

@hpustudent
Copy link
Author

It is really the latest version , okio version :1.6.0 , okhttp: 2.5.0.

@shobhitpuri
Copy link
Contributor

Is there a solution for this?

@darrachequesne
Copy link
Member

Closed due to inactivity, please reopen if needed.

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

No branches or pull requests

4 participants