# Logstash 5.4 - Repeated deserialization errors and losing data with Persistent Queues **URL:** \ **Category:** Logstash\ **Created:** [July 1, 2017, 1:56am UTC](https://discuss.elastic.co/t/logstash-5-4-repeated-deserialization-errors-and-losing-data-with-persistent-queues/91503 "2017-07-01T01:56:47Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)\ **Post date:** [July 3, 2017, 8:14am UTC](https://discuss.elastic.co/t/logstash-5-4-repeated-deserialization-errors-and-losing-data-with-persistent-queues/91503/5 "2017-07-03T08:14:27Z")
It seems like a Java Byte Array has somehow made it into an Event before it is put in the Persistent Queue. Clearly this is able to be serialized via CBOR into binary form (which is then persisted). However, when it is taken out the queue, the binary deserialize to Map works because the error backtrace says: ```auto at org.logstash.Event.(Event.java:66) at org.logstash.Event.fromSerializableMap(Event.java:212) at org.logstash.Event.deserialize(Event.java:399) ``` At this line `Event.java:66`, a new Event is created from the Map, but we don't have a BiValue handler for Byte arrays at the moment. There are two ways to fix this: 1. Detect and eliminate the source of the Byte array. **_For this we need your config and some lines of scrubbed data_**. 2. Add a Byte array Bivalue to the Java Event. For this we need to change some LS core code and release a patch. You might be able to achieve (1) without new LS core code (maybe an input plugin will need a fix). But for (2) you will have to wait for us to fix the Event code. --- _[View the full topic](https://discuss.elastic.co/t/logstash-5-4-repeated-deserialization-errors-and-losing-data-with-persistent-queues/91503)._