public static class RegistryClient.UnacceptableStalenessException extends RegistryClient.RegistryClientRuntimeException
RegistryClient methods when their internal copy of the Registry's
catalogue is "too old".
Most RegistryClient implementations will keep an internal copy of the Registry's
catalogue in memory, in order to perform faster queries, and to counteract EWP network failure
due to a temporary EWP Registry Service downtime. If, for some reason, the internal copy of the
catalogue grows "too old", then this exception will be raised. (Note, that it can also be
caused by improper configuration of your server, not necessarily by the Registry Service's
downtime.)
The exact definition of "too old" depends on particular implementation. For example,
ClientImpl allows you to set your own limit of staleness via
ClientImplOptions.setMaxAcceptableStaleness(long). You can also check
RegistryClient.getExpiryDate() manually and make decisions based on its value.
| Constructor and Description |
|---|
UnacceptableStalenessException() |
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toStringCopyright © 2017. All rights reserved.