Unexpected token ” + token + “; expected – Elasticsearch Error How To Solve Related Issues

Unexpected token ” + token + “; expected – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch 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 causing 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: .

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 discover the cause of many errors and provides suitable actionable recommendations (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) {


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 SyntaxError: Unexpected token function – Async Await Nodejs -views 165,818 ,score 120

Uglify SyntaxError: Unexpected token: punc ()) -views   58,369,score 60



About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now