This issue started about 5 days ago (October 28th). Disconnects were happening about every half hour to everyone on the server. It has progressively gotten worse. Currently, it happens every 2-3 minutes and the game is pretty much unplayable. Every disconnect gives me the following error: "Internal Exception: io.netty.handler.timeout.ReadTimeoutException".
After a couple of disconnects, I get a different error message and then I am no longer able to join any servers for a while. "Failed to login: the authentication are currently down for maintenance."
Any help resolving this issue would be greatly appreciated.
edit// It looks like I'm only getting disconnected when I'm running around possibly generating new terrain. I just sat atop a column of dirt for 30 minutes and didn't get disconnected. The minute I started running accross the terrain I got disconnected.
edit #2// Error only encountered while exploring new content/chunks. Seems stable if I stay in old areas.
Linked issues
Comments 5
Yes, I've been browsing through all the tickets relating to it but most people seem to be having issues loging onto their servers. I can usually log on fine but can't stay on. I'm not sure why they're all being lumped together. It's a serious issue and I wish we'd get an update on what's going on. Have they figured out what it is? Are they working on it?
That's a very good question. It's hard to say what the ETA is as I haven't seen any. It may be a while as Grum and Dinnerbone are at Minecon.
I finally got someone to port me back to my old home built before 1.7.2 and my connection is now stable. However, I can't explore new content because of the issue mentioned in this ticket.
Definitely not a duplicate of reconnect/join problems.
I am frequently disconnected when I am on either one of my two multiplayer vanilla 1.7.2 servers
a) when more than two people are on with me,
b) those players are in different chunks, and
c) when I attempt to leave the chunk I am in and enter a new one
So you know, this will be closed as moderators are calling these duplicate tickets to a "resolved" one, which hasn't been resolved.