spring-amqp

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

I'm using @RabbitListener annotation and SimpleRabbitListenerContainerFactory bean for parallel execution of rabbitmq messages and setting the min and max concurrent consumers in the following way : @Bean public SimpleRabbitListenerContainerFactory rabbitListenerContainerFactory() { SimpleRabbitListenerContainerFactory factory = new SimpleRabbitListenerContainerFactory(); factory.setConnectionFactory(connectionFactory()); factory.setConcurrentConsumers(MIN_RABBIT_CONCURRENT_CONSUMERS); factory.setMaxConcurrentConsumers(MAX_RABBIT_CONCURRENT_CONSUMERS); factory.setConsecutiveActiveTrigger(1);

I am trying to connect to RabbitMQ over SSL. I have followed the RabbitMQ SSL documentation linked here https://www.rabbitmq.com/ssl.html As per RabbitMQ SSL documentation connecting using SSLv3 and TLSv1 is not recommeded due to known vulnerabilities. Due to this I have disabled these protocols on RabbitMQ as per instructions. I am using spring-amqp 1.4.3 to connect to RabbitMQ. Plese find below code snippet ApplicationContext context = new GenericXmlApplicationContext("classpath:/testConfig/testrabbit-context.xml"); RabbitTemplate template = context.getBean(RabbitTemplate.class);

I hava following spring xml configuration <bean id="connectionFactory" class="org.springframework.amqp.rabbit.connection.CachingConnectionFactory"> <constructor-arg value="xxxxxxxx"/> <property name="username" value="xxxxx"/> <property name="password" value="xxxxx"/> <property name="channelCacheSize" value="25"/> <property name="virtualHost" value="/"/> <property name="port" value="3453"/> </bean> <rabbit:template id="tutorialTemplate" connection-factory="connectionFactory"/> <!-- 1st queue --> <rabbit:queue id="veliteQueue" name="ES_queue" durable="true" auto-delete="false" exclusive="false"/

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