Logger.errorcause.getMessage; – How to solve related issues

Average Read Time

2 Mins

Logger.errorcause.getMessage; – 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 ” Logger.errorcause.getMessage; ” 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 “Logger.error(cause.getMessage());” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 ActionListener.wrap(bulkResponse -> {
                    List retryTokenIds = new ArrayList();
                    for (BulkItemResponse bulkItemResponse : bulkResponse.getItems()) {
                        if (bulkItemResponse.isFailed()) {
                            Throwable cause = bulkItemResponse.getFailure().getCause();
                            traceLog("(bwc) invalidate tokens";  cause);
                            if (isShardNotAvailableException(cause)) {
                            } else if ((cause instanceof VersionConflictEngineException) == false){
                                // We don't handle VersionConflictEngineException; the ticket has been invalidated


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

Analyze your cluster