8000 fix: Do not use directExecutor() for the publish callback when ordering is enabled by michaelpri10 · Pull Request #2693 · googleapis/java-pubsub · GitHub
[go: up one dir, main page]

Skip to content

fix: Do not use directExecutor() for the publish callback when ordering is enabled#2693

Merged
michaelpri10 merged 1 commit intogoogleapis:mainfrom
michaelpri10:ccm
Feb 17, 2026
Merged

fix: Do not use directExecutor() for the publish callback when ordering is enabled#2693
michaelpri10 merged 1 commit intogoogleapis:mainfrom
michaelpri10:ccm

Conversation

@michaelpri10
Copy link
Contributor

This prevents a ConcurrentModificationException from occurring that is caused by the use of the directExecutor() when scheduling a callback, which can cause lock isolation to be broken.

Fixes #2377

@michaelpri10 michaelpri10 requested a review from a team February 16, 2026 23:01
@product-auto-label product-auto-label bot added size: xs Pull request size is extra small. api: pubsub Issues related to the googleapis/java-pubsub API. labels Feb 16, 2026
@michaelpri10
Copy link
Contributor Author

/gcbrun

BF3B

@michaelpri10 michaelpri10 merged commit c7ecd2b into googleapis:main Feb 17, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: pubsub Issues related to the googleapis/java-pubsub API. size: xs Pull request size is extra small.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PubSub: ConcurrentModificationException when publishing messages with ordering keys

2 participants

0