-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.7.2
-
None
-
Minecraft 1.7, Mac OS.X (10.8.4)
-
Unconfirmed
-
Survival
When I connect to a server, 99% of the time, about 30 seconds after I have connected I get kicked and I get this error:
io.netty.handler.timeout.ReadTimeoutException
It happends on nearly every servers I try to connect to. I was going fine in 1.7.2 until now, but since this morning, this error occurs. I know I am not the only one that gets this error, lots of people do.
This was already posted here, but, it was marked as Fixed, but I still get it !
Please fix this issue.
Thanks
Rieunieuniau
EDIT: When you connect, you can't do anything and only the chunck that you are on is loaded. The other chunks are just like air and you fall very slowly if you jump.
Ryan Clayton added a comment.
To any of the moderators. Please do not mark this as a duplicate issue (MC-34947). The prior issue has been closed and marked as resolved but it most certainly is not. This is effecting MANY users and opening a new bug was the only way to bring this issue into focus for the devs.
- duplicates
-
- Reopened
[MC-38689] io.netty.handler.timeout.ReadTimeoutException error after connecting to servers
Here's the situation I'm seeing:
1. Everything starts off fine. The server has a 20 player limit, it reaches 20 by mid-day.
2. Nothing special is recorded in the log prior to the event.
3. Something happens. <--
4. After that, all users are disconnected at the same time without an error on the server side. They all just log out. User report seeing the Netty timeout error on their end, but the server log says nothing special except that they all logged out together, in the same second.
5. This happens every minute for several minutes.
6. The problem self-corrects after a while, everything is fine again.
7. Repeat.
I looked at the Netty documentation, and there seems to be a 30 second timeout. Maybe this is too short.
http://netty.io/4.0/api/io/netty/handler/timeout/IdleStateHandler.html
Is it my network conditions? Perhaps. Prior to 1.7, we would go through poor network conditions without these constant mass disconnect. Instead, players all had "a bunch of lag" but they could usually still chat.
Of course, they mark it as resolved. How are we supposed to get this fixed it they keep closing them and claiming it's fixed?
Having this issue on my 1.7.2 servers on a regular basis, it is even causing lag issues.
To any of the moderators. Please do not mark this as a duplicate issue (MC-34947). The prior issue has been closed and marked as resolved but it most certainly is not. This is effecting MANY users and opening a new bug was the only way to bring this issue into focus for the devs.
It is resolved as duplicate of
MC-37175