[#2398] FutureBrokerInfoTimeout is missed due to logic operator error - #2399
Merged
cshannon merged 2 commits intoAug 5, 2026
Merged
Conversation
cshannon
requested changes
Aug 4, 2026
…its timeout The timed get loop's condition uses || between the not-disposed check and the deadline check, so the loop runs until disposal regardless of the caller's timeout. Widens FutureBrokerInfo to package-private so the test drives the real class. Two of four scenarios fail until the condition is corrected.
Correct the loop condition from || to && so the timed get exits when EITHER the bridge is disposed OR the deadline expires. Previously a peer that never delivered its BrokerInfo parked the bridge start thread until disposal, ignoring the caller's timeout.
mattrpav
force-pushed
the
amq-gh-2398-futurebrokerinfotimeout
branch
from
August 5, 2026 21:09
7311a15 to
a4802a7
Compare
cshannon
approved these changes
Aug 5, 2026
cshannon
left a comment
cshannon
left a comment
Contributor
There was a problem hiding this comment.
LGTM assuming tests pass
cshannon
added a commit
that referenced
this pull request
Aug 6, 2026
…#2399) (#2409) * [#2398] Add test proving FutureBrokerInfo.get(timeout) ignores its timeout The timed get loop's condition uses || between the not-disposed check and the deadline check, so the loop runs until disposal regardless of the caller's timeout. Widens FutureBrokerInfo to package-private so the test drives the real class. Two of four scenarios fail until the condition is corrected. * Fix FutureBrokerInfo.get(timeout) to honor its timeout Correct the loop condition from || to && so the timed get exits when EITHER the bridge is disposed OR the deadline expires. Previously a peer that never delivered its BrokerInfo parked the bridge start thread until disposal, ignoring the caller's timeout. (cherry picked from commit c6f85bc) Co-authored-by: Matt Pavlovich <mattrpav@apache.org>
cshannon
added a commit
that referenced
this pull request
Aug 6, 2026
…#2399) (#2410) * [#2398] Add test proving FutureBrokerInfo.get(timeout) ignores its timeout The timed get loop's condition uses || between the not-disposed check and the deadline check, so the loop runs until disposal regardless of the caller's timeout. Widens FutureBrokerInfo to package-private so the test drives the real class. Two of four scenarios fail until the condition is corrected. * Fix FutureBrokerInfo.get(timeout) to honor its timeout Correct the loop condition from || to && so the timed get exits when EITHER the bridge is disposed OR the deadline expires. Previously a peer that never delivered its BrokerInfo parked the bridge start thread until disposal, ignoring the caller's timeout. (cherry picked from commit c6f85bc) Co-authored-by: Matt Pavlovich <mattrpav@apache.org>
cshannon
added a commit
that referenced
this pull request
Aug 6, 2026
…#2399) (#2411) * [#2398] Add test proving FutureBrokerInfo.get(timeout) ignores its timeout The timed get loop's condition uses || between the not-disposed check and the deadline check, so the loop runs until disposal regardless of the caller's timeout. Widens FutureBrokerInfo to package-private so the test drives the real class. Two of four scenarios fail until the condition is corrected. * Fix FutureBrokerInfo.get(timeout) to honor its timeout Correct the loop condition from || to && so the timed get exits when EITHER the bridge is disposed OR the deadline expires. Previously a peer that never delivered its BrokerInfo parked the bridge start thread until disposal, ignoring the caller's timeout. Co-authored-by: Matt Pavlovich <mattrpav@apache.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.