Question

当channelTransacted（true）将错误而不是重新排队时将消息抛入死信队列时，如何设置监听器容器？当我不使用channelTransacted时，一切正常，我可以看到死信队列中的消息。

@Bean(name = "amqpInboundEsignRequest")
public IntegrationFlow amqpInbound(ConnectionFactory connectionFactory, PlatformTransactionManager transactionManager) {
    return IntegrationFlows.from(
            Amqp.inboundAdapter(connectionFactory, esignIAutoRequestQueue())
                    .acknowledgeMode(AcknowledgeMode.AUTO)
                    .messageConverter(new Jackson2JsonMessageConverter())
                    .autoStartup(false)
                    .defaultRequeueRejected(false)
                    //.channelTransacted(true) // dead letter does not work
                    //.transactionManager(transactionManager) // dead letter does not work
    )
            .log("amqpInbound.start-process")
            .handle(p -> {
                throw new RuntimeException("Something wrong!");
            })
            .get();
}

修改

这些是依赖项的版本。

[INFO] +- org.springframework.boot:spring-boot-starter-amqp:jar:1.5.9.RELEASE:compile
[INFO] |  +- org.springframework:spring-messaging:jar:4.3.13.RELEASE:compile
[INFO] |  \- org.springframework.amqp:spring-rabbit:jar:1.7.4.RELEASE:compile
[INFO] |     +- com.rabbitmq:http-client:jar:1.1.1.RELEASE:compile
[INFO] |     +- com.rabbitmq:amqp-client:jar:4.0.3:compile
[INFO] |     +- org.springframework.retry:spring-retry:jar:1.2.1.RELEASE:compile
[INFO] |     \- org.springframework.amqp:spring-amqp:jar:1.7.4.RELEASE:compile

[INFO] +- org.springframework.boot:spring-boot-starter-integration:jar:1.5.9.RELEASE:compile
[INFO] |  +- org.springframework.integration:spring-integration-core:jar:4.3.12.RELEASE:compile
[INFO] |  \- org.springframework.integration:spring-integration-java-dsl:jar:1.2.3.RELEASE:compile
[INFO] |     \- org.reactivestreams:reactive-streams:jar:1.0.0:compile

我希望事务与外部事务db（PlatformTransactionManager）同步。当我在侦听器容器上设置transactionManager（transactionManager）时，它总是会重新排队。

Answer 1

您使用的是哪个版本？我刚刚使用Spring Integration 5.0.2和Spring AMQP 2.0.2以及Spring Integration 4.3.14和Spring AMQP 1.7.6测试channelTransacted=true，一切都按预期工作，失败的消息进入DLQ。 / p>

@SpringBootApplication
public class So48914749Application {

    public static void main(String[] args) {
        SpringApplication.run(So48914749Application.class, args);
    }

    @Bean
    public IntegrationFlow amqpInbound(ConnectionFactory connectionFactory) {
        return IntegrationFlows.from(
                Amqp.inboundAdapter(connectionFactory, "foo")
                        .acknowledgeMode(AcknowledgeMode.AUTO)
                        .messageConverter(new Jackson2JsonMessageConverter())
                        .autoStartup(true)
                        .defaultRequeueRejected(false)
                        .channelTransacted(true) // dead letter does not work
        // .transactionManager(transactionManager) // dead letter does not work
        )
                .log("amqpInbound.start-process")
                .handle(p -> {
                    throw new RuntimeException("Something wrong!");
                })
                .get();
    }

    @Bean
    public Queue queue() {
        return QueueBuilder.durable("foo")
                .withArgument("x-dead-letter-exchange", "")
                .withArgument("x-dead-letter-routing-key", "dlq")
                .build();
    }

    @Bean
    public Queue dlq() {
        return new Queue("dlq");
    }

    @RabbitListener(queues = "dlq")
    public void dlq(Message in) {
        System.out.println(in);
    }

}

结果：

（正文：＆＃39; [B @ 17793549（字节[8]）＆＃39; MessageProperties [headers = {x-first-death-exchange =，x-death = [{reason = rejected，count = 1，exchange =，time = Wed Feb 21 16:43:48 EST 2018，routing-keys = [foo]，queue = foo}]，x-first-death-reason = rejected，x-first-death-queue = foo}，timestamp = null，messageId = null，userId = null，receivedUserId = null，appId = null，clusterId = null，type = null，correlationId = null，correlationIdString = null，replyTo = null，contentType = null，contentEncoding = null ，contentLength = 0，deliveryMode = null，receivedDeliveryMode = NON_PERSISTENT，expiration = null，priority = null，redelivered = false，receivedExchange =，receivedRoutingKey = dlq，receivedDelay = null，deliveryTag = 4，messageCount = 0，consumerTag = amq.ctag- dOypXDkkQ5Hvw2W9cUIpzg，consumerQueue = dlq]）

修改

将来请更准确;无论是否提供了事务管理器，您的问题都意味着发生了同样的问题。

见the second NOTE under A note on Rollback of Received Messages。这是在2.0中修复的。

在1.7.x中，我们必须默认保留旧行为，以实现向后兼容性。 1.7.x documentation解释了您必须将alwaysRequeueWithTxManagerRollback设置为false以获得新的（一致的）行为。

这是一个侦听器容器属性，因此您需要连接一个容器并将其注入入站通道适配器。

spring amqp dead letter queue不能与事务

1 个答案: