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

Issue 5337: Handle closed event loops #5410

Open
wants to merge 1 commit into
base: 4.x
Choose a base branch
from

Conversation

Onkelborg
Copy link

Motivation:

The issue that this attempts to correct is #5337

There is a race condition in case someone attempts to send a message on the eventbus to an address at the same time as the receiver is being undeployed - if the receiver's context has it's own worker pool, that worker pool will get shutdown, and it won't be possible to enqueue the operation to receive the message, and exception will be thrown. This affects both send and publish - in the latter case, an undefined number of registered consumers will receive the message in case this race condition affects one of the receivers.

I've written unit tests for both local and clustered eventbus, and I think that the code coverage for them are quite comprehensive.

Conformance:

  • Eclipse Contributor Agreement has been signed.
  • I think I've managed to following the code style guidelines

@Onkelborg Onkelborg force-pushed the issue-5337-handle-closed-event-loops branch from b192a21 to 4f37985 Compare November 29, 2024 07:46
…ly handle if the receiving context's event loop has been shutdown
@Onkelborg Onkelborg force-pushed the issue-5337-handle-closed-event-loops branch from 4f37985 to 109688d Compare November 29, 2024 07:55
@vietj vietj added this to the 4.5.12 milestone Dec 3, 2024
@vietj vietj self-requested a review December 3, 2024 09:07
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.

2 participants