Class ExecutionError

  • All Implemented Interfaces:
    java.io.Serializable

    @GwtCompatible
    public class ExecutionError
    extends java.lang.Error
    Error variant of ExecutionException. As with ExecutionException, the error's cause comes from a failed task, possibly run in another thread. That cause should itself be an Error; if not, use ExecutionException or UncheckedExecutionException. This allows the client code to continue to distinguish between exceptions and errors, even when they come from other threads.
    Since:
    10.0
    Author:
    Chris Povirk
    See Also:
    Serialized Form
    • Method Summary

      • Methods inherited from class java.lang.Throwable

        addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
      • Methods inherited from class java.lang.Object

        clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
    • Constructor Detail

      • ExecutionError

        @Deprecated
        protected ExecutionError()
        Deprecated.
        Prefer ExecutionError(@org.jspecify.annotations.Nullable java.lang.Error) a constructor that accepts a cause: Users of this class typically expect for instances to have a non-null cause. At the moment, you can usually still preserve behavior by passing an explicit null cause. Note, however, that passing an explicit null cause prevents anyone from calling Throwable.initCause(java.lang.Throwable) later, so it is not quite equivalent to using a constructor that omits the cause.
        Creates a new instance with null as its detail message and no cause.
      • ExecutionError

        @Deprecated
        protected ExecutionError​(@Nullable java.lang.String message)
        Deprecated.
        Prefer ExecutionError(@org.jspecify.annotations.Nullable java.lang.String,@org.jspecify.annotations.Nullable java.lang.Error) a constructor that accepts a cause: Users of this class typically expect for instances to have a non-null cause. At the moment, you can usually still preserve behavior by passing an explicit null cause. Note, however, that passing an explicit null cause prevents anyone from calling Throwable.initCause(java.lang.Throwable) later, so it is not quite equivalent to using a constructor that omits the cause.
        Creates a new instance with the given detail message and no cause.
      • ExecutionError

        public ExecutionError​(@Nullable java.lang.String message,
                              @Nullable java.lang.Error cause)
        Creates a new instance with the given detail message and cause. Prefer to provide a non-nullable cause, as many users expect to find one.
      • ExecutionError

        public ExecutionError​(@Nullable java.lang.Error cause)
        Creates a new instance with null as its detail message and the given cause. Prefer to provide a non-nullable cause, as many users expect to find one.