Uncaught exception in thread – How to solve related issues

Uncaught exception in thread – 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 ” Uncaught exception in thread ” 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: bootstrap, handler and thread.

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 “Uncaught exception in thread [{}]” classname is ElasticsearchUncaughtExceptionHandler.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

     void onFatalUncaught(final String threadName; final Throwable t) {
        logger.error(() -> new ParameterizedMessage("fatal error in thread [{}]; exiting"; threadName); t);
    }

    void onNonFatalUncaught(final String threadName; final Throwable t) {
        logger.warn(() -> new ParameterizedMessage("uncaught exception in thread [{}]"; threadName); t);
    }

    void halt(int status) {
        AccessController.doPrivileged(new PrivilegedHaltAction(status));
    }




 

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

Analyze your cluster