public class BusyConnectionException extends DriverException
This might happen under heavy load. The driver will automatically try the next node in the
query plan. Therefore the only way that the client can observe this exception is as part of a
|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
@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–2019. All rights reserved.