发送端同步确认机制:waitForConfirms()函数可以确认一条消息或多条消息是否发送(只关心发送给exchange)成功
//开启发送端确认机制
channel.confirmSelect();
//回调函数同步确认消息是否成功发送给exchange
if (channel.waitForConfirms()) {
LOG.info("message send");
} else {
LOG.debug("message error");
}
发送端异步确认机制:发送端会另起一个线程在不确定的时机调用回调函数,验证消息是否发送成功
ConfirmListener confirmListener = new ConfirmListener() {
@Override
public void handleAck(long deliveryTag, boolean multiple) throws IOException {
LOG.info("message success, deliveryTag:{} multiple:{}", deliveryTag, multiple);
}
@Override
public void handleNack(long deliveryTag, boolean multiple) throws IOException {
LOG.info("message fail, deliveryTag:{} multiple:{}", deliveryTag, multiple);
}
};
final ConfirmCallback confirmCallback = (deliveryTag,multiple)->{
LOG.info("deliveryTag:{} ,multiple:{}");
};
//添加异步回调监听器
channel.addConfirmListener(confirmListener);
消息返回机制:如果消息不能被路由,exchange会把未被路由的message返回给发送端
//添加消息返回监听器,当 exchange 不能把 message 正确路由时调用回调函数返回消息
channel.addReturnListener((replyCode, replyText, exchange, routingKey, properties, body) -> {
LOG.debug("\n" +
"message exchange ERROR, replyCode:{}, \n" +
"replyText:{}, \n" +
"exchange:{}, \n" +
"routingKey:{}, \n+" +
"properties:{}, \n" +
"body:{}", replyCode, replyText, exchange, routingKey, properties, new String(body));
});
//开启消息返回机制:把 mandatory设置为 true
channel.basicPublish(exchangeName, "drink.chinese.testError", true, null, message.getBytes());
消费端手动确认,确保消息被业务正确处理后再确认
//关闭自动ACK:autoAck置为 false
channel.basicConsume(queueName,false,deliverCallback,consumerTag -> {});
DeliverCallback deliverCallback = ((consumerTag, message) -> {
LOG.info("message:{}",new String(message.getBody()));
//消息处理完成后进行手动 Ack
channel.basicAck(message.getEnvelope().getDeliveryTag(),false);
});
消费端限流机制:对于监听同一条队列的多个消费端,默认情况下message是循环平均分发,这会导致消费速度慢的消费端的消息积压等情况
//在未被确认的消息的数量小于 prefetchCount前 队列不会往这个 channel发送新的消息
channel.basicQos(2);
消息过期,防止消息长时间积压 ,可以设置每条消息的过期时间,也可以设置队列中的消息的统一的过期时间,另外可以设置队列本身的过期时间
发送消息时设置消息的过期时间
//设置消息发送的参数
AMQP.BasicProperties basicProperties = new AMQP.BasicProperties()
.builder()
.expiration("15000")
.build();
//通过basicProperties配置消息属性
channel.basicPublish(exchangeName, "drink.chinese", true, basicProperties, message.getBytes());
设置队列中统一的消息过期时间
Map<String, Object> argsMap = new HashMap<>(16);
argsMap.put("x-message-ttl", 15000);//参数参考地址:https://www.rabbitmq.com/ttl.html
//通过argsMap设置队列属性
channel.queueDeclare(queueName, true, false, false, argsMap);
死信队列:消息成为死信的可能 1.消息被消费端拒绝 reject/nack 并且 requeue=false;2.消息过期;3.超过队列长度
Map<String, Object> argsMap = new HashMap<>(16);
//定义死信要被发送到的exchange
argsMap.put("x-dead-letter-exchange", "exchange.dlx");
channel.queueDeclare(queueName, true, false, false, argsMap);