Skip to content
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

Add Exception handling at RpcService #5901

Conversation

chimp1984
Copy link
Contributor

At shutdown the executor can throw a RejectedExecutionException which is expected as we shut down the executor immediately.
If not thrown at shutdown or exception is not a RejectedExecutionException
we log a warning and re-throw the exception (to avoid change of behaviour
of current version). The exception is likely not handled by callers and goes up to
the uncaught exception handler.

is expected as we shut down the executor immediately.
If not thrown at shutdown or exception is not a RejectedExecutionException
we log a warning and re-throw the exception (to avoid change of behaviour
of current version). The exception is likely not handled by callers and goes up to
the uncaught exception handler.
@ripcurlx ripcurlx added this to the v1.8.0 milestone Dec 8, 2021
Copy link
Contributor

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK - Tested it on Mainnet

@bisq-github-admin-3
Copy link
Contributor

Still merging this as the Codacy complaint isn't correct in this scenario.

@bisq-github-admin-3 bisq-github-admin-3 merged commit be4cbcd into bisq-network:master Dec 9, 2021
@chimp1984 chimp1984 deleted the handle-RejectedExecutionException-in-RpcService branch December 9, 2021 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants