When attempting to connect to a 14w28a server, the client is disconnected and is shown the following message:
Connection Lost
Internal Exception: io.netty.handler.codec.DecoderException: java.lang.IndexOutOfBoundsException: readerIndex(1389927) + length(135424) exceeds writerIndex(1477223): UnpooledHeapByteBuf(ridx: 1389927, widx : 1477223, cap: 1477223/1477223)
The server logs the following message:
[11:56:18 INFO]: Guy lost connection: TranslatableComponent{key='disconnect.genericReason', args=[Internal Exception: java.io.IOException: An established connection was aborted by the software in your host machine], siblings=[], style=Style{hasParent=false, color=null, bold=null, italic=null, underlined=null, obfuscated=null, clickEvent=null, hoverEvent=null, insertion=null}}
Comments 16
For me the numbers are different but otherwise it's the same error message. Other players can join the server just fine, it's just me who can't log in. Our world doesn't have any barrier blocks in it.
I am using an amplified world though, and there are blocks at the height limit, which may be the issue. There is an IndexOutOfBounds exception, so the probably might be that the buffer containing the blocks might not have room for 256 blocks, perhaps this was an off by one error and one of the devs accidentally only allocated space for 255.
I wasn't trying to say the problem would be barrier blocks, I was trying to point out their height, and we could replicate the issue by placing blocks at the top y-layer (y 255 i.e. y 256).
Probably an off-by-one error by the devs...
This problem is still occurring, I don't know how to fix it. Does anyone have any ideas? Will I be able to ever get back in?
Affects 15w40a: http://bilder.ding.si/2qO496ZPwI.png
L3viathan: MC-89643.
This looks a lot like an error we were getting on an existing world a friend was hosting.
In our case, the culprit was barrier blocks that were placed a y 256, removing them stopped the issue as far as we can tell.
I don't know if this is the exact same problem, though, but the error looks the same