StompBrokerRelay depends on deprecated RabbitMQ STOMP feature: transient_nonexcl_queues

[gabxdev1]

Hello,

I'm using Spring Boot 3.4.4 with STOMP over WebSocket and the StompBrokerRelay setup.
I noticed that Spring is relying on the RabbitMQ STOMP plugin to automatically create and manage queues for /user/queue/... destinations.

However, the STOMP plugin uses the now-deprecated behavior transient_nonexcl_queues, which leads to the creation of non-exclusive, durable queues that are not automatically deleted when users disconnect.

This results in hundreds of persistent queues being left behind in RabbitMQ, which could cause issues over time.

My setup:

• Spring Boot: 3.4.4
• RabbitMQ Docker image: rabbitmq:4.0.7-management-alpine
• STOMP plugin enabled via rabbitmq-plugins enable rabbitmq_stomp

RabbitMQ logs display the warning: transient_nonexcl_queues is deprecated and will be removed in a future release

Is there any plan to:

• Support exclusive or auto-delete queues for /user/... destinations?
• Add TTL configuration for these queues?
• Offer an alternative strategy that avoids this deprecated feature?

Reference:
RabbitMQ blog post about this deprecation:
https://www.rabbitmq.com/blog/2021/08/21/4.0-deprecation-announcements#removal-of-transient-non-exclusive-queues

Thank you!

[artembilan]

Looks like a duplication of: #34540.