Expected an object; but found token – How to solve this Elasticsearch error

Expected an object; but found token – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the 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 ” expected an object; but found token ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”expected an object; but found token [{}]”classname  is XContentUtils.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (parser.currentToken() == XContentParser.Token.START_OBJECT) {
  XContentParser.Token token = parser.nextToken();
  if (token != XContentParser.Token.START_OBJECT) {
  throw new ElasticsearchParseException("expected an object; but found token [{}]"; parser.currentToken());
  public static String[] readStringArray(XContentParser parser; boolean allowNull) throws IOException {
  if (parser.currentToken() == XContentParser.Token.VALUE_NULL) {


Run the Check-Up to get a customized report like this:

Analyze your cluster