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

Websocket connection closed with 1001 when high loading (1M messaging) #86

Closed
jumperchen opened this issue May 3, 2017 · 4 comments
Closed

Comments

@jumperchen
Copy link

We found that okhttp websocket client implementation is not stable when sending with 1M messages. (refer to this issue - square/okhttp#3317)
Other Java implementation seem to be more stable. Like Tyrus, NV-Websocket-Client).

So it would be better if you could provide a way to switch the Java client implementation.

@b95505017
Copy link
Collaborator

Please checkout #85, you could implement your own WebSocket.Factory interface now.

@jumperchen
Copy link
Author

Thanks, I will try with that mechanism. (I tested by hard code with NV-Websocket-Client, it works well without any issue :) )

@jumperchen
Copy link
Author

@b95505017
Do you know about the schedule when the 0.8.4 version will be released? (about the fixed of #85)

@b95505017
Copy link
Collaborator

I don't have the permission to release, must discuss with @nkzawa .

@nkzawa nkzawa closed this as completed Jul 14, 2017
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

3 participants