Expecting Json Field name token after the Start Object token – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Expecting Json Field name token after the Start Object token ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Expecting Json Field name token after the Start Object token” classname is AutodetectResultsParser.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             }
            if (token == XContentParser.Token.END_ARRAY) {
                consumeAndCloseStream(in);
                return false;
            } else if (token != XContentParser.Token.START_OBJECT) {
                logger.error("Expecting Json Field name token after the Start Object token");
                consumeAndCloseStream(in);
                throw new ElasticsearchParseException("unexpected token [" + token + "]");
            }
            return true;
        }




 

Try AutoOps to detect and fix issues in your cluster:

See how it works

Analyze Your Cluster

Skip to content