Skip to content

Tag: spring-amqp

Does Spring AMQP CorrelationData getFuture wait indefinitely without timeout?

In the context of Publisher confirms, when waiting for the CorrelationData’s future (SettableListenableFuture#get()) – does it wait indefinitely or is there a timeout configured under the water? Answer It does wait indefinitely. There is just no any opinion and everything is delegated directly to the java.util.concurrent.FutureTask internally in the org.springframework.util.concurrent.SettableListenableFuture implementation. Not sure why the question, but in normal situation

Dynamically configure RabbitMQ users and permissions with Java Spring AMQP

For security reasons, I want to configure separate user accounts with specific permissions to isolates queues in RabbitMQ. As users need to be a dynamic (adding new, removing deactivated…) I would like to achieve this with Java Spring AMQP. Creating queues, exchanges and bindings is possible with The RabbitMQ Management HTTP API provides also features regarding the user management, as

Synchronous publish for rabbitmq

I want to have two sets API for the clients to publish messages sync send(no retry, fail immediately and send status back to the clients synchronously) async send (publisher and confirm callback, with retry, log and drop the message after certain retries). I am able to implement this by enabling confirm and return. Is there any way to implement Synchronous

When publisher confirms are enabled, queue length limit is set and overflow is set to reject-publish,why cause in confirm callback I received is null?

I am learning Queue Length Limit(, as it says, queue is set to ‘x-max-length:10’,and ‘x-overflow:reject-publish’, and also, I enable publisher confirms. So, when the number of messages in the queue reaches 10, the publisher will be informed of the reject via a basic.nack message. And it is: my confirm callback got a false ack, but cause is null. I’m wondering

Spring Rabbit MQ listener issues

My Configuration Class is below:- The DTO is :- The Snippet for publishing the message is:- And the snippet to listen the message is:- The issue is the logs here are not coming up but if I try with The snippet below then it works:- it does goes to the logs but how to get the TestDto in that case?