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
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
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
I have two different java spring projects that communicate through rabbitmq. I’m trying to send a java object but I get this error message: I’m aware that the problem is in the classpath that should be the same in both producer and consumer, but since each project has a different name I can’t make the classpath the same even though
I watched a tutorial that explains how to integrate RabbitMQ into Spring Boot app. In the tutorial, the ReceiveMessageHandler.java (Consumer) and SendMessageController.java (Producer) classes were in …
I am learning Queue Length Limit(https://www.rabbitmq.com/maxlength.html), 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
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?