public class HeartbeatException extends DriverException
Heartbeat queries are sent automatically on idle connections, to ensure that they are still
alive. If a heartbeat query fails, the connection is closed, and all pending queries are aborted.
The exception will be passed to
RetryPolicy.onRequestAborted(Request, Throwable, int),
which decides what to do next (the default policy retries the query on the next node).
|Constructor and Description|
|Modifier and Type||Method and Description|
Copy the exception.
The address of the node that encountered the error.
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public HeartbeatException(@NonNull SocketAddress address, @Nullable String message, @Nullable Throwable cause)
public HeartbeatException(SocketAddress address, String message, ExecutionInfo executionInfo, Throwable cause)
@NonNull public SocketAddress getAddress()
@NonNull public DriverException copy()
This returns a new exception, equivalent to the original one, except that because a new object is created in the current thread, the top-most element in the stacktrace of the exception will refer to the current thread. The original exception may or may not be included as the copy's cause, depending on whether that is deemed useful (this is left to the discretion of each implementation).
This is intended for the synchronous wrapper methods of the driver, in order to produce a more user-friendly stack trace (that includes the line in the user code where the driver rethrew the error).
Copyright © 2017–2021. All rights reserved.