spring-rabbitmq

I'm using SpringAMQP with Rabbit template. How to send messages directly to Queues omitting Exchange? How can i do it? How can i do it? You can't; publishers don't know about queues; just exchanges and routing keys. However, all queues are bound to the default exchange ( "" ) with the queue name as its routing key. If you are using Spring AMQP's RabbitTemplate , it is configured to publish to the default exchange by default, so you can use convertAndSend("myQueue", "foo")` Or even... template.setDefaultRoutingKey("myQueue"); then template.convertAndSend("foo"); or template.send(aMessage); 来源：

I have read this fragment of docs: RabbitMQ Automatic Connection/Topology recovery Since the first version of Spring AMQP, the framework has provided its own connection and channel recovery in the event of a broker failure. Also, as discussed in Section 3.1.10, “Configuring the broker”, the RabbitAdmin will re-declare any infrastructure beans (queues etc) when the connection is re-established. It therefore does not rely on the Auto Recovery that is now provided by the amqp-client library. Spring AMQP now uses the 4.0.x version of amqp-client, which has auto recovery enabled by default. Spring

Its like " Houston we have a problem here " where I need to schedule/delay a message for 5 minutes after it fails on the first attempt to process an event. I have implemented dead letter exchange in this scenario. The messages on failing, route to the DLX --> Retry Queue and comes back to work queue after a TTL of 5 minutes for another attempt. Here is the configuration I am using: public class RabbitMQConfig { @Bean(name = "work") @Primary Queue workQueue() { return new Queue(WORK_QUEUE, true, false, false, null); } @Bean(name = "workExchange") @Primary TopicExchange workExchange() { return

My SpringBoot configuration contains very strong retry policy for rabbitTemplate retries spring: rabbitmq: template: retry: enabled: true initial-interval: 500 max-attempts: 10 multiplier: 5 max-interval: 60000 The problem with this configuration is when health endpoint is called and rabbitMQ is down, the connections hangs for really long time. Adding properties like spring.rabbitmq.connection-timeout=500 or spring.rabbitmq.template.receive-timeout=500 or spring.rabbitmq.template.reply-timeout=500 or spring.rabbitmq.requested-heartbeat=1 does not help, since the retry.multiplier=5 , so it will

This is the scenario - There are multiple app servers. Browser can connect via websocket to any app server. The app servers (consumers) are all listening on a particular queue. As soon as a web socket connection is received, the particular app server binds the queue with a routing key {userId} to a direct exchange. I want a message sent to the direct exchange with the routing key {userId} to be received by only the particular app server where the binding has occured. Is a direct exchange the right exchange to use in this case? Or should some other type of exchange be used? I'm using spring

I did read this reference: https://www.rabbitmq.com/dlx.html , however it doesn't resolve my doubts, namely: In case of accepting message there is no problem - spring-rabbitmq send ack and everthing is fine, DLX doesn't know about acked message. The problem is in case rejecting answer, namely what about throwing MessageConverterException ? This message is removed or moved to DLX ? And what about in case other exception ? For example Exception ? It is removed/requeued/moved to DLX ? Edit after answer of @Gary I think, that after answer's @Gary I should add more details about my case and some

I have developed asynchronous Spring Cloud Stream services, and I am trying to develop an edge service that uses @MessagingGateway to provide synchronous access to services that are async by nature. I am currently getting the following stack trace: Caused by: org.springframework.messaging.core.DestinationResolutionException: no output-channel or replyChannel header available at org.springframework.integration.handler.AbstractMessageProducingHandler.sendOutput(AbstractMessageProducingHandler.java:355) at org.springframework.integration.handler.AbstractMessageProducingHandler.produceOutput

How to acknowledge the messages manually without using auto acknowledgement. Is there a way to use this along with the @RabbitListener and @EnableRabbit style of configuration. Most of the documentation tells us to use SimpleMessageListenerContainer along with ChannelAwareMessageListener . However using that we lose the flexibility that is provided with the annotations. I have configured my service as below : @Service public class EventReceiver { @Autowired private MessageSender messageSender; @RabbitListener(queues = "${eventqueue}") public void receiveMessage(Order order) throws Exception {