Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by sagonfor7
, 1 year ago
Not enough readable bytes - Need 191, maximum is 179
via Google Groups by sagonfor7, 1 year ago
Not enough readable bytes - Need 191, maximum is 179
via https://bugzilla.redhat.com/bugzilla/ by Miroslav Novak, 2 years ago
Not enough readable bytes - Need 409600, maximum is 204795
via https://bugzilla.redhat.com/bugzilla/ by Miroslav Novak, 2 years ago
via GitHub by shyamraj242
, 1 year ago
Not enough readable bytes - Need 132, maximum is 120
java.lang.IndexOutOfBoundsException: Not enough readable bytes - Need 191, maximum is 179 at org.jboss.netty.buffer.AbstractChannelBuffer.checkReadableBytes(AbstractChannelBuffer.java:668)[netty-3.9.4.Final.jar:na] at org.jboss.netty.buffer.AbstractChannelBuffer.readBytes(AbstractChannelBuffer.java:338)[netty-3.9.4.Final.jar:na] at org.jboss.netty.buffer.AbstractChannelBuffer.readBytes(AbstractChannelBuffer.java:344)[netty-3.9.4.Final.jar:na] at org.hbase.async.SecureRpcHelper.wrap(SecureRpcHelper.java:235)[asynchbase-1.7.2.jar:na] at org.hbase.async.RegionClient.encode(RegionClient.java:1385)[asynchbase-1.7.2.jar:na]