Skip to content

Conversation

jdcormie
Copy link
Member

All BinderTransport transactions are oneway which means uncaught Exceptions processing them are merely logged locally and not propagated to the peer. This PR adds a top level catch block that handles the unexpected by shutting down the whole transport. This makes our peer aware of the problem immediately (instead of relying on a deadline) and gives clients a fresh transport instance to handle any retries.

All BinderTransport transactions are oneway which means uncaught
Exceptions during processing are merely logged locally and not
propagated to the peer. Instead, we add a top level catch block
that handles the unexpected by shutting down the whole transport. This
makes our peer aware of the problem immediately (instead of relying on a
deadline) and gives clients a fresh transport instance to handle any
retries.
@jdcormie jdcormie requested a review from markb74 April 21, 2023 22:53
@jdcormie jdcormie marked this pull request as ready for review April 24, 2023 16:03
Copy link
Contributor

@markb74 markb74 left a comment

Choose a reason for hiding this comment

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

Sorry for the delay, thanks for this!

@jdcormie jdcormie merged commit 87fe410 into grpc:master Apr 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants