spring-amqp:通道关闭并收到 NACKS 消息

spring-amqp: Channel shutdown with NACKS RECEIVED message

在 RabbitMQ 总线上使用重负载的 spring-amqp,我们有时会从 org.springframework.amqp.rabbit.connection.CachingConnectionFactory 获取日志说: 频道关闭:清洁频道关闭;协议方法:#method(reply-code=200, reply-text=NACKS RECEIVED, class-id=0, method-id=0)

你能解释一下这个日志吗,为什么它是错误级别的? 我们有什么需要调整的吗? 预先感谢您的回答。

如果超时未返回所有发布者确认,频道将抛出异常...

@Override
public void waitForConfirmsOrDie(long timeout)
    throws IOException, InterruptedException, TimeoutException
{
    try {
        if (!waitForConfirms(timeout)) {
            close(AMQP.REPLY_SUCCESS, "NACKS RECEIVED", true, null, false);
            throw new IOException("nacks received");
        }
    } catch (TimeoutException e) {
        close(AMQP.PRECONDITION_FAILED, "TIMEOUT WAITING FOR ACK");
        throw(e);
    }
}

如果回复文本是 OK...

DefaultChannelCloseLogger 将仅跳过正常关闭 (200)
/**
 * Return true if the {@link ShutdownSignalException} reason is AMQP.Channel.Close and
 * the reply code was AMQP.REPLY_SUCCESS (200) and the text equals "OK".
 * @param sig the exception.
 * @return true for a normal channel close.
 */
public static boolean isNormalChannelClose(ShutdownSignalException sig) {
    Method shutdownReason = sig.getReason();
    return isNormalShutdown(sig) ||
            (shutdownReason instanceof AMQP.Channel.Close
                && AMQP.REPLY_SUCCESS == ((AMQP.Channel.Close) shutdownReason).getReplyCode()
                && "OK".equals(((AMQP.Channel.Close) shutdownReason).getReplyText()));
}

如果您想忽略这些错误,您可以配置自定义关闭异常记录器:

/**
 * Set the strategy for logging close exceptions; by default, if a channel is closed due to a failed
 * passive queue declaration, it is logged at debug level. Normal channel closes (200 OK) are not
 * logged. All others are logged at ERROR level (unless access is refused due to an exclusive consumer
 * condition, in which case, it is logged at INFO level).
 * @param closeExceptionLogger the {@link ConditionalExceptionLogger}.
 * @since 1.5
 */
public void setCloseExceptionLogger(ConditionalExceptionLogger closeExceptionLogger) {
    Assert.notNull(closeExceptionLogger, "'closeExceptionLogger' cannot be null");
    this.closeExceptionLogger = closeExceptionLogger;
    if (this.publisherConnectionFactory != null) {
        this.publisherConnectionFactory.setCloseExceptionLogger(closeExceptionLogger);
    }
}