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

Introduce options to configure the creation of an event-bus consumer #5474

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

vietj
Copy link
Member

@vietj vietj commented Feb 6, 2025

Introduce MessageConsumerOptions to configure the creation of an event-bus consumer and deprecate message consumer max buffered message upper bound setter.

Motivation:

The event-bus message consumer has a dynamic max buffered messages upper bound. This dynamic bound makes difficult to implement the message flow and requires a custom implementation. Instead this should be configured when the consumer is created.

Changes:

Introduce MessageConsumerOptions that provides all the necessary details to create a consumer (address, localOnly, maxBufferedMessages). Consumer setMaxBufferedMessages is deprecated in favour of using options.

@vietj vietj force-pushed the message-consumer-options branch from 86221f3 to 8c586ac Compare February 6, 2025 12:30
@vietj vietj added this to the 4.5.13 milestone Feb 6, 2025
@vietj vietj self-assigned this Feb 6, 2025
@vietj vietj force-pushed the message-consumer-options branch from 8c586ac to 017fb45 Compare February 6, 2025 12:34
…and deprecate message consumer max buffered message upper bound setter.

Motivation:

The event-bus message consumer has a dynamic max buffered messages upper bound. This dynamic bound makes difficult to implement the message flow and requires a custom implementation. Instead this should be configured when the consumer is created.

Changes:

Introduce MessageConsumerOptions that provides all the necessary details to create a consumer (address, localOnly, maxBufferedMessages). Consumer setMaxBufferedMessages is deprecated in favour of using options.
@vietj vietj force-pushed the message-consumer-options branch from 017fb45 to 11c5e2f Compare February 6, 2025 13:35
@vietj vietj merged commit 9f91d2b into 4.x Feb 6, 2025
7 checks passed
@vietj vietj deleted the message-consumer-options branch February 6, 2025 13:54
@vietj vietj linked an issue Feb 6, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove MessageConsumer dynamic max buffered message
1 participant