Unexpected token ” + token + “; expected – How to solve this Elasticsearch error

Average Read Time

2 Mins

Unexpected token ” + token + “; expected – 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 ” unexpected token ” + token + “; expected ” 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: Node.

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”unexpected token [” + token + “]; expected [{]”classname  is StoredScriptSource.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

XContentParser parser = xContentType.xContent()
  .createParser(NamedXContentRegistry.EMPTY; LoggingDeprecationHandler.INSTANCE; stream)) {
  Token token = parser.nextToken();
  if (token != Token.START_OBJECT) {
  throw new ParsingException(parser.getTokenLocation(); "unexpected token [" + token + "]; expected [{]");
  token = parser.nextToken();
  if (token == Token.END_OBJECT) {


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

Analyze your cluster