Spring Cloud Dataflow自定义应用RabbitMQ绑定配置问题排查

场景 #

开发了一个注入Time OOTB应用主函数的自定义应用，希望在SCDF部署流时自定义RabbitMQ的队列和Exchange行为。通过API POST请求部署时配置了RabbitMQ相关属性，但首次发送payload时出现错误，导致首个消息丢失，无法路由到死信队列。同时，本地application-properties文件中的配置无效果。

当前部署配置（API POST参数） #

{
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.auto-bind-dlq":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.deadLetterExchangeType":"topic",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.deadLetterQueueName":"NameOfStream.dlq",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.republish-to-dlq":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.dlq-dead-letter-exchange":"DLX",
  "app.appExample.spring.cloud.stream.rabbit.bindings.input.consumer.exchangeAutoDelete":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.consumer.exchangeAutoDelete":"true"
}

报错信息 #

2023-05-11 15:40:21.196 ERROR [log-sink,,] 1 --- [.0.109.185:5672] o.s.a.r.c.CachingConnectionFactory       : Shutdown Signal: channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'x-dead-letter-exchange' for queue 'test.http.test' in vhost '/': received none but current is the value 'DLX' of type 'longstr', class-id=50, method-id=10)

无效的本地配置（application-properties） #

spring.cloud.stream.bindings.output.destination=timeDemo-output
spring.cloud.stream.function.bindings.timeExtractor-out-0=output

spring.cloud.stream.rabbit.bindings.output.consumer.autoBindDlq=true
spring.cloud.stream.rabbit.bindings.output.consumer.dlq-dead-letter-exchange=DLX
spring.cloud.stream.rabbit.bindings.output.consumer.republish-to-dlq=true

spring.cloud.stream.rabbit.bindings.output.consumer.exchangeAutoDelete=true
spring.cloud.stream.rabbit.bindings.output.consumer.deadLetterExchangeType=topic
spring.cloud.stream.rabbit.bindings.output.consumer.dlqExpires=1000
spring.cloud.stream.rabbit.bindings.output.consumer.expires=1000
spring.cloud.stream.rabbit.bindings.output.consumer.exchangeAutoDelete=true

环境 #

• Spring Cloud Dataflow服务器
• Skipper服务器
• Docker部署的RabbitMQ服务器

解决方案 #

1. 修正配置的作用域与属性方向错误 #

• API配置中混了producer和consumer属性：output.consumer.exchangeAutoDelete无效，output是生产者端，应使用output.producer.exchangeAutoDelete；input属于消费者端，对应input.consumer.*属性。
• 本地配置错误地给output绑定了consumer属性，output是生产者出口，所有RabbitMQ配置应使用spring.cloud.stream.rabbit.bindings.output.producer.*前缀，而非consumer。

2. 解决队列预条件不匹配问题 #

报错提示队列test.http.test的x-dead-letter-exchange参数不匹配，说明该队列已存在，且死信交换配置与当前请求冲突，可通过以下方式解决：

• 部署流前，清理RabbitMQ中已存在的相关队列和Exchange（包括死信队列）。
• 若无法清理，添加配置spring.cloud.stream.rabbit.bindings.output.producer.queueDeclarationRetries=3和spring.cloud.stream.rabbit.bindings.output.producer.queueDeclarationRetryInterval=1000，允许队列声明重试以适配已存在的配置。

3. 正确配置死信交换与队列关联 #

修正后的API部署配置示例：

{
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.auto-bind-dlq":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.deadLetterExchangeType":"topic",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.deadLetterQueueName":"NameOfStream.dlq",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.republish-to-dlq":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.dlq-dead-letter-exchange":"DLX",
  "app.appExample.spring.cloud.stream.rabbit.bindings.output.producer.exchangeAutoDelete":"true",
  "app.appExample.spring.cloud.stream.rabbit.bindings.input.consumer.exchangeAutoDelete":"true"
}

4. 确认SCDF配置优先级 #

SCDF部署时传递的配置优先级高于应用本地application-properties，因此本地配置不生效是正常的，所有自定义配置需通过SCDF部署API或Dashboard传递。

5. 验证死信交换存在性 #

如果DLX是自定义交换，需确保它已在RabbitMQ中创建，或添加配置spring.cloud.stream.rabbit.bindings.output.producer.deadLetterExchangeDurable=true，让生产者自动创建该交换（若不存在）。

内容的提问来源于stack exchange，提问作者Emmanuel_Arreola