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.

Sign up for GitHub

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

Jump to bottom

Handle STOMP messages to user destination in order #31395

Closed
rstoyanchev opened this issue Oct 10, 2023 · 0 comments
Closed

Handle STOMP messages to user destination in order #31395

rstoyanchev opened this issue Oct 10, 2023 · 0 comments
Assignees
@rstoyanchev
Labels
in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Milestone
6.1.0-RC1

Comments

@rstoyanchev
Copy link
Contributor

After #21798, messages on the clientInboundChannel can be handled sequentially within a session by setting StompEndpointRegistry#preserveReceiveOrder. This in addition to the MessageBrokerRegistry#preservePublishOrder that does the same for messages on the clientOutboundChannel.

UserDestinationMessageHandler subscribes to clientInboundChannel and brokerChannel and also handles messages from the client. Therefore it makes sense to extend the support for StompEndpointRegistry#preserveReceiveOrder so when it is enabled, messages with user destinations are handled sequentially by user.
@rstoyanchev rstoyanchev added in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement labels Oct 10, 2023
@rstoyanchev rstoyanchev added this to the 6.1.0-RC1 milestone Oct 10, 2023
@rstoyanchev rstoyanchev self-assigned this Oct 10, 2023
@rstoyanchev rstoyanchev mentioned this issue Oct 10, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rstoyanchev rstoyanchev

Labels
in: messaging Issues in messaging modules (jms, messaging) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.0-RC1
Development

No branches or pull requests
1 participant
@rstoyanchev