Krist Pregracke
- Lazauya
- lazauya
- Europe/Stockholm
- Yes
- No
MC-34938
Low
I will get this error occasionally when trying to join a server: Internal Exception: io.netty
,handler.timeout.ReadTimeoutExceptionI will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
Internal Exception: io.netty,handler.timeout.ReadTimeoutExceptionInternal Exception: io.netty.handler.timeout.ReadTimeoutException
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
EDIT: As seen on this post, it generally happens for people with worse connections, though I never got this error in previous versions.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E
DIT: As seen on this post, it generally happens for people with worse connections, though I never got this error in previous versions.I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
EDIT: This bug is still prevalent, although it does not occur as often.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
EDIT: This bug is still prevalent (and really frustrating), although it does not occur as often.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
EDIT: This bug is still prevalent (and really frustrating), although it does not occur as often. I have gotten this error many times since 1.7.2 release.
I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
EDIT: This bug is still prevalent (and really frustrating), although it does not occur as often. I have gotten this error many times since 1.7.
2release.I will get this error occasionally when trying to join a server: Internal Exception: io.netty.handler.timeout.ReadTimeoutException
E̶D̶I̶T̶:̶ ̶A̶s̶ ̶s̶e̶e̶n̶ ̶o̶n̶ ̶t̶h̶i̶s̶ ̶p̶o̶s̶t̶,̶ ̶i̶t̶ ̶g̶e̶n̶e̶r̶a̶l̶l̶y̶ ̶h̶a̶p̶p̶e̶n̶s̶ ̶f̶o̶r̶ ̶p̶e̶o̶p̶l̶e̶ ̶w̶i̶t̶h̶ ̶w̶o̶r̶s̶e̶ ̶c̶o̶n̶n̶e̶c̶t̶i̶o̶n̶s̶,̶ ̶t̶h̶o̶u̶g̶h̶ ̶I̶ ̶n̶e̶v̶e̶r̶ ̶g̶o̶t̶ ̶t̶h̶i̶s̶ ̶e̶r̶r̶o̶r̶ ̶i̶n̶ ̶p̶r̶e̶v̶i̶o̶u̶s̶ v̶e̶r̶s̶i̶o̶n̶s̶.
EDIT: It has apparently been confirmed that even with faster internet speeds, the error still occurs. Also, as pointed out in this post, it happens frequently when trying to connect to your own server too, even when using a port-forwarding program like Hamachi. This error has only been occurring since 13w41a.
EDIT: This bug is still prevalent (and really frustrating), although it does not occur as often. I have gotten this error many times since 1.7.4 release.
The server when ran will not stop "Generating new properties file" (It doesn't actually), which eats up memory and
computing power. This bug makes it almost impossible to play!The server when ran will not stop "Generating new properties file" (It doesn't actually), which eats up memory and slows down the console to an unusable rate.
I had to switch back to the 13w43a .exe in order to play with the new features. I have a suspicion that this might just be a simple Java permission bug, but Java has full permissions on my system. I am hoping that a .exe gets released soon for 1.7 .
I haven't personally gotten this error yet in 1.7, but I figured I'd update the post as I saw you guys were.
Hey! I found a fix. You need to set the default program that opens .jars to javaw; it turns out that this was a permissions bug, as it will ask if you would like to allow access or not.
This bug makes the game virtually unplayable on a server. There is no way to break the cycle if there is no one around to help, and in certain cases you are not even teleported back to the correct coordinates, causing you to die and lose your items.
@JimmyZJX
Here's a log of the incident using your jar:
https://drive.google.com/file/d/0B-2DQ3g04GV0cExURThGLWZ5UXM/view?usp=sharing
For me the bug is extremely persistent—it's more rare that it doesn't happen.
EDIT: This is when I enter nether portals. This only seems to happen when I start in the nether and go from the nether to the overworld. It doesn't happen (or at least happens very rarely) when I enter the nether from the overworld.