Announcement

Collapse
No announcement yet.

Internal Exception: io.netty.handler.timeout.readtimeoutexception

Collapse
X
Collapse
Who has read this thread:
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Internal Exception: io.netty.handler.timeout.readtimeoutexception

    Did some research. Turns out this is caused by corrupted chunks.

    I was at the End Portal shortly after it successfully reset the End. I was in there with qscgukp and EraserRainofHood (if I remember the usernames properly).

    Did the End Portal cause a chunk error or is this common?
    w-what is this autism aura??
    if I dont gook this lolisama now..........
    our western culture will be forever....

    ..mememized

    #2
    Originally posted by Th3_3p1c_G4m3r View Post
    Did some research. Turns out this is caused by corrupted chunks.

    I was at the End Portal shortly after it successfully reset the End. I was in there with qscgukp and EraserRainofHood (if I remember the usernames properly).

    Did the End Portal cause a chunk error or is this common?
    ReadTimeoutException is caused when the server stops responding ._.
    My software doesn't have bugs. It just develops random features.

    Do you have a hour emergency call systems broadcasting radio station WNYW or Internet Explorer?
    Well? Which one?

    Cyros admits the truth: http://i.snag.gy/GTy14.jpg

    Comment


      #3
      It's an exception caused by read timeouts

      Comment


        #4
        Originally posted by Remilia_Scarlet View Post
        It's an exception caused by read timeouts
        That's handled by Io Netty.

        Weird name.
        sigpic
        Spoiler:


        Comment


          #5
          Originally posted by Tenko View Post
          ReadTimeoutException is caused when the server stops responding ._.
          Originally posted by Remilia_Scarlet View Post
          It's an exception caused by read timeouts
          No. Time outs are caused by not cleaning your room or breaking plates and kicking your big brother. this is first grade stuff people, come on

          Comment


            #6
            No I keep getting the same error message. Yesterday I was able to log on fine but as of now I'm getting this error message as well. I fixed it the first time by updating my game to 1.7.4, This time I tried to 1.7.9 but it says the server is on 1.7.5 so I switched to 1.7.5 and Now I got This Message. "Authentication servers are down. Please try again later, sorry!"
            So how much longer am I going to have to wait before I can log back on?

            Comment


              #7
              Well if the auth servers are down, that's Mojang's problem. Not ours. We literally cannot do anything about it.


              Sent from my iPhone using Tapatalk

              Comment

              Working...
              X