Kryo Deserialization fails with "KryoException: Buffer underflow"

Question

I use Kryo to write Objects into byte arrays. It works fine. But when the byte arrays are converted into the Objects, it throws, com.esotericsoftware.kryo.KryoException: Buffer underflow. exception.

This is my deserialization:

        Kryo k=new Kryo();
        Input input=new Input(byteArrayOfObject);           
        Object o=k.readObject(input,ObjectClass.class);

Furthermore, always the object type cannot be defined in my application. At the final process, the class conversion happens. Therefore,

How can I solve above deserialization error
Is there a way to create Object without giving the class into readObject(...,ClassName) ?

I'm facing same issue? Is this resolved? I tried below suggestions, did not help.. — Sharath, Jul 23 '16 at 20:44

score 18 · Answer 1 · edited Apr 20 '16 at 06:30

18

This happened to me when I was not correctly closing the Output / Input types. You need to make sure Kryo flushes everything but doing output.flush() or output.close().

Second, look into kryo.writeClassAndObject(). You can then do kryo.readClassAndObject() and cast your object to the type it is supposed to be.

edited Apr 20 '16 at 06:30

Anubian Noob

13,426
6
53
75

answered Feb 28 '15 at 23:44

sydraz

653
6
12

1

Helps me a lot! In my case I had ByteArrayOutputStream stream1 = new ByteArrayOutputStream(); and Output output1 = Output(stream1). The goal was to serialize some Object into byte array using kryo.writeClassAndObject(output, someObject);.The important thing was to call, output1.close(); before calling stream1.toByteArray(); Hope this helps someone to save a time trying to quickstart Kryo! – Yurii Bratchuk Mar 30 '18 at 11:38
modern kryo does flush before close – guai Aug 26 '19 at 18:16

score 4 · Answer 2 · answered May 02 '16 at 22:19

4

This happend to me when I used the serializer in multiple threads. It's not thread safe, so if you use it in that way, it may give you "Buffer underflow" or other exceptions.

answered May 02 '16 at 22:19

Henry Hu

524
4
12

This idea is echoed by the answer here: https://github.com/EsotericSoftware/kryo/issues/128#issuecomment-28249144 – Luke Machowski Jun 10 '17 at 14:17

score 4 · Answer 3 · answered Jan 04 '18 at 21:06

I saw this error because of a true Java serialization issue; my class definition was not the same on the producer and consumer side (two different applications) and as a result I got this exception.

Just wanted to leave this as an FYI if you hadn't checked that yet.

Kryo Deserialization fails with "KryoException: Buffer underflow"

3 Answers3

Linked