Compatibility issue between 5.5.0 and 5.6.0 about kryo HOT 2 CLOSED

Thanks for the detailed bug report @sldab!

There have been no changes to URISerializer between 5.5.0 and 5.6.0 and only 3 PRs that could potentially affect serialization: https://github.com/EsotericSoftware/kryo/releases/tag/kryo-parent-5.6.0

Do you use setOptimizedGenerics(false) in your Kryo config? If not, then the first PR does not affect you at all. The two other PRs only deal with BigDecimalSerializer.

Please try to write a reproducer test-case for this. Serialize RefreshTokenEntry with Kryo 5.5.0, copy the resulting bytes and try to deserialize the bytes into a new RefreshTokenEntry instance with the new field using Kryo 5.6.0.

from kryo.

Thanks for your quick response @theigl.

I don't have setOptimizedGenerics(false) in my Kryo config.

I've downgraded to Kryo 5.5.0 and the issue still persisted, so it's not a compatiiblity issue as suspected.

Comparing a new record with an existing one revealed that the new record had two additional bytes before the affected fields, so the issue is likely caused by the new field. I've managed to manually patch the byte data of one of the records.

Yet, I don't understand why this issue didn't occur when upgrading the other instances of our system.

from kryo.