RabbitMQ的两种消息确认,publisherConfirms 和 publisherReturns。
- publisherConfirms:消息发送到exchange,返回成功或者失败。
- publishReturns:消息从exchange到queue,发送成功或者失败。
具体操作看下方代码
- 消费者与生产者两方都要配置
CachingConnectionFactory
,其中将publisherConfirms,publishReturns开启,默认都是false
@Bean
@ConditionalOnClass
public CachingConnectionFactory connectionFactory() {
CachingConnectionFactory factory = new CachingConnectionFactory();
factory.setHost("127.0.0.1");
factory.setUsername("guest");
factory.setPassword("guest");
factory.setVirtualHost("/");
factory.setPublisherConfirms(true);
factory.setPublisherReturns(true);
return factory;
}
- 消息Procuder端:设置RabbitTemplate相关属性
@Bean
@ConditionalOnClass
public RabbitTemplate template(CachingConnectionFactory connectionFactory) {
RabbitTemplate template = new RabbitTemplate(connectionFactory);
template.setConfirmCallback((correlationData, ack, cause) -> {
LOGGER.info("confirm callback publish --> status of publihs message: {}", ack);
LOGGER.info("confirm callback publish --> correlationData: {}", correlationData);
LOGGER.info("confirm callback publish --> cause: {}", cause);
});
// 如果设置ReturnCallback,必须将Mandatory设置为true
template.setMandatory(true);
template.setReturnCallback((message, replyCode, replyText,
exchange, routingKey) -> {
LOGGER.info("return callbak exchange: {}, routingKey: {}, message:{}", exchange, routingKey, new String(message.getBody(), StandardCharsets.UTF_8));
});
return template;
}
相关代码就是如此简单,验证时可以干掉exchange,这样就可以验证confirm。将queue与exchange解绑,可以验证returnCallback