Skip to content

StompBrokerRelay: Adapt to RabbitMQ deprecation of transient, non-exclusive queues #34540

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
Closed
acutus opened this issue Mar 5, 2025 · 2 comments
Closed

StompBrokerRelay: Adapt to RabbitMQ deprecation of transient, non-exclusive queues #34540

acutus opened this issue Mar 5, 2025 · 2 comments
Labels
for: external-project Needs a fix in external project in: messaging Issues in messaging modules (jms, messaging)

Comments

@acutus
Copy link

acutus commented Mar 5, 2025 •
edited
Loading

spring-messaging:6.1.12

RabbitMQ has deprecated transient, non-exclusive queues (see rabbitmq/rabbitmq-server#13009 and https://www.rabbitmq.com/release-information/deprecated-features-list).

StompBrokerRelay (StompBrokerRelayMessageHandler?) should consider this when creating STOMP-subscriptions and switch to durable client-named queues as a default, instead of the current transient non-exclusive queues created for subscriptions.
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Mar 5, 2025
@acutus acutus mentioned this issue Mar 5, 2025
Open
@jhoeller jhoeller added the in: messaging Issues in messaging modules (jms, messaging) label Mar 19, 2025
@artembilan artembilan mentioned this issue Apr 10, 2025
Closed
@bclozel bclozel marked this as a duplicate of #34734 Apr 11, 2025
@artembilan
Copy link
Member

The deprecation warning from STOMP plugin in RabbitMQ is going to be addressed in version 4.2 this Fall: rabbitmq/rabbitmq-server#13016.

Meanwhile a {"durable", "true"} header can be set from the application on send and subscribe commands.

Nothing to do from the Framework perspective.

@sbrannen
Copy link
Member

Thanks for the research and feedback, @artembilan!

In light of that, I am closing this issue.

@sbrannen sbrannen closed this as not planned Won't fix, can't repro, duplicate, stale Apr 15, 2025
@sbrannen sbrannen added for: external-project Needs a fix in external project and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
for: external-project Needs a fix in external project in: messaging Issues in messaging modules (jms, messaging)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@sbrannen @artembilan @jhoeller @acutus @spring-projects-issues