# jakarta.json.stream.JsonParsingException when deserializing data retrieved from Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Tags:** language-clients\ **Created:** [September 19, 2023, 1:04pm UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367 "2023-09-19T13:04:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Georgi\_Nikolov](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Georgi\_Nikolov](https://discuss.elastic.co/u/Georgi_Nikolov)\ **Post date:** [September 19, 2023, 1:04pm UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367/1 "2023-09-19T13:04:26Z")
for some time now I have been trying to incorporate the Elastic Java 8.10 client into my code, I have a big ELK stack with a lot of data. I am trying to fetch continuously data from it, but I am encountering some inconsistent behavior. My code is following the Elastic tutorial on their website and I have a simple function to get the data: ```java /** * Method for querying a search in ELK using search_after. * @param search_size * @param index * @param sort_options * @param field * @param value * @return SearchResponse * @throws IOException on failed search */ public final SearchResponse querySearch(final int search_size, final String index, final List sort_options, final List search_after, final String field, final String value) throws IOException { SearchResponse result = this.el_client.search(s -> s .index(index) .size(search_size) .sort(sort_options) .query(q -> q .term(t -> t .field(field) .value(v -> v.stringValue(value)) )), JsonData.class); return result; } ``` The strange thing is that it works fine for some time, but then I always receive the following error: ```auto Error deserializing co.elastic.clients.elasticsearch.core.search.Hit: jakarta.json.stream.JsonParsingException: Illegal unquoted character ((CTRL-CHAR, code 10)): has to be escaped using backslash to be included in name ``` it is inconsistent as it happens at random entries retrieved from Elasticsearch, I looked the previous entries that were retrieved and it is never the same time window (i am using the @timestamp field to cross-reference which entries might provoke the error) Here is a GitHubgist with the stack trace: [gist:a28bd2e4b4732ed25837b4fdddf2468d ยท GitHub](https://gist.github.com/GeorgiNikolovRMA/a28bd2e4b4732ed25837b4fdddf2468d) At this point I have the feeling that the error is not from my code, but how the Elastic API sends the data and then the transformation from the raw JSON to JsonData. I tried using Object instead, but the same thing happens. Is there a way to sanitize the JSON at the moment of fetching it or any way to correct this strange behavior? ---
**Author:** ![swallez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swallez/32/11972_2.png) [@swallez](https://discuss.elastic.co/u/swallez)\ **Post date:** [September 19, 2023, 1:49pm UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367/2 "2023-09-19T13:49:39Z")
This is indeed rather strange: the error indicates that the JSON content sent by the server is malformed. Can you log the `SearchRequest` that causes these errors to replay them in the Kibana console to examine the JSON returned by Elasticsearch? `JsonpUtils.toJsonString()` can be used for that. ---
**Author:** ![Georgi\_Nikolov](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Georgi\_Nikolov](https://discuss.elastic.co/u/Georgi_Nikolov)\ **Post date:** [September 19, 2023, 3:32pm UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367/3 "2023-09-19T15:32:28Z")
Thank you for the reply, how should I log the SearchRequest and response? Is there a special method of the SearchRequest I can call providing the specific stream to output to? ---
**Author:** ![swallez](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swallez/32/11972_2.png) [@swallez](https://discuss.elastic.co/u/swallez)\ **Post date:** [September 19, 2023, 4:09pm UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367/5 "2023-09-19T16:09:07Z")
You have to refactor the code a bit: ```java SearchResponse result = this.el_client.search(s -> s .index(index) .size(search_size) ... return result; ``` has to become something like: ```java SearchRequest request = SearchRequest.of(s -> s .index(index) .size(search_size) ... try { SearchResponse result = this.el_client.search(request, JsonData.class); return result; } catch (JsonpMappingException e) { String requestJson = JsonpUtils.toJsonString(request, this.es_client_); JsonpMapper mapper = this.es_client._transport().jsonpMapper(); logger.error("Decoding error. Request is: " + JsonpUtils.toJsonString(request, mapper), e); throw e; } ``` This should log the requests that caused a failure, which you can they copy/paste in the Kibana developer console to see what the response looks like. ---
**Author:** ![Georgi\_Nikolov](https://avatars.discourse-cdn.com/v4/letter/g/6de8d8/32.png) [@Georgi\_Nikolov](https://discuss.elastic.co/u/Georgi_Nikolov)\ **Post date:** [September 20, 2023, 11:44am UTC](https://discuss.elastic.co/t/jakarta-json-stream-jsonparsingexception-when-deserializing-data-retrieved-from-elasticsearch/343367/6 "2023-09-20T11:44:41Z")
So I adapted my code as you suggested and ran the program. As stated previously, Elastic is holding a large quantity of records, so probably I will need to let it run for multiple hours. The strange thing is that it wildly varies when the Mapping error occurs, so I don't know when exactly it might crash. I tried to use the range query to try and search for entries in a time-window where previously the errors occurred, but nothing so far. Once, i have the request and test it in the Kibana Developer Console, I will come back to you with the results. Also while I am staring at the screen, I'm wondering when the program will crash and if you think there might be an influence of the amount of records retrieved at once? Originally I was retrieving the max amount of records (100) and then using searchAfter to continue the retrieval. Now I switched to 5, for legibility reasons and haven't encountered any problems so far.