public class ClosedConnectionException extends DriverException
For example, this can happen if the node is unresponsive and a heartbeat query failed, or if the node was forced down.
The driver will always retry these requests on the next node transparently. Therefore, the
only way to observe this exception is as part of an
|Constructor and Description|
|Modifier and Type||Method and Description|
Copy the exception.
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public ClosedConnectionException(@NonNull String message)
@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–2020. All rights reserved.