-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When an other KER is unavailable, the current KER should not log a lot of CompletionExceptions
caused by contacting it anyway.
#463
Comments
This error might prevent the creation of a new Smart Connector in which case it is more impatctful than I thought. This error pops up in the Generic Adapter logs with the following message:
|
After further research, we are able to reproduce errors similar to the ones above using the following procedure:
Although it might take a while, the addition of a new Smart Connector succeeds and the KER remains in a correct state despite the exception in the log. This also becomes clear from the code, where in case of an exception the exception is logged and |
Another development in this issue. The creation of a Smart Connector seems to indeed fail when there are unavailable other KERs (currently investigating why it worked in my tests anyway), because the
|
When a remote KER becomes unavailable, the SCs it hosts should not be involved in any data exchange. The exception below, shows that the OtherKnowledgeBaseStore tries to retrieve details about a SC that is hosted by a currently unavailable KER.
This is probably caused by a bug where the
RemoteKerConnection.remoteKerDetails
is not set tonull
in thesendToRemoteSmartConnector
method when an error occurs and this causes the SCs to be returned when populating resulting a the failed contacted and Exception above.The text was updated successfully, but these errors were encountered: