Sorry to re-create this bug, but after some searching, I think there's no open issue currently tracking this precise problem.
Original issue (marked Resolved): MC-34947
Quoting one of the commenters on MC-34947: this describes our situation:
"I can consistently produce this error by successfully logging into the server, clicking disconnect, and attempting to reconnect to the same server. The screen pauses at "Logging in..." and then gives this error when the login times out."
We're still seeing this in the 1.7 pre-release (another user has commented the same on the original issue)
The problem repro's consistently on both Windows and Linux hosting; across multiple players on my servers, for the last few snapshots.
Not sure how big the impact will be if you roll out 1.7 update without a fix, but worth thinking about!
Related issues
Comments
@William it sounds like you have a slightly different issue, but it could be related anyway due to changes in the network libs.
Quoting one of the commenters on MC-34947: this describes my situation:
"I can consistently produce this error by successfully logging into the server, clicking disconnect, and attempting to reconnect to the same server. The screen pauses at "Logging in..." and then gives this error when the login times out."
Still have this problem with 1.7.1.
Duplicate of MC-34947 - If you have not, please use the search function in the future, to see if your bug has already been submitted. If you could not find the original report, please comment with the keywords you searched for.
Thanks for reopening the original issue. It wasn't clear to me if comments on that one would be noticed!
I'm getting the same error in the 1.7 Pre-Release. I haven't been able to play any of the last few snapshots in multiplayer because of this problem. I get in, I can play for a couple minutes, then get kicked. Come back in, and I need to figure out where I am since I'm not where I was when I got kicked. By the time I figure out where I am and where I need to go, I get kicked again.
You keep marking it "Resolved", but the problem is not fixed. Can you please fix this problem so it doesn't keep hjappening?