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

Read timeout instead of disconnect if all servers in priority list are not reachable #52

Closed
fuzzybot opened this issue Jul 1, 2016 · 0 comments
Assignees

Comments

@fuzzybot
Copy link
Contributor

fuzzybot commented Jul 1, 2016

Client logs,
[22:51:40] [Client thread/INFO]: Connecting to localhost, 25577
[22:51:44] [Client thread/INFO]: [CHAT] Could not connect to default or fallback server, please try again later: java.net.ConnectException

10-20 seconds later client disconnects with
Connection Lost
ReadTimeoutException : null

Server logs,
22:52:41 [INFO] [/127.0.0.1:62668] <-> InitialHandler has connected
22:53:14 [WARNING] [/127.0.0.1:62668|fuzzy_bot] -> UpstreamBridge - read timed out
22:53:14 [INFO] [fuzzy_bot] disconnected with: ReadTimeoutException : null
22:53:14 [INFO] [/127.0.0.1:62668|fuzzy_bot] -> UpstreamBridge has disconnected

Bungeecord upstream is correctly disconnecting the client instead. Tested this without the recent ServerKickEvent improvements patch and it is still happening.

@fuzzybot fuzzybot self-assigned this Jul 1, 2016
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

1 participant