使用 RabbitMQ 作为消息总线的 Spring XD 中的耗尽消息
Exhausted messages in Spring XD with RabbitMQ as the message bus
我有一个 Spring XD 1.2.0 安装，其中一台服务器和几个使用 RabbitMQ 作为消息总线的容器，我在日志中看到很多 WARN 消息，例如：
2017-02-05T22:51:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=14, messageCount=0])
2017-02-05T22:52:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=15, messageCount=0])
2017-02-05T22:53:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=16, messageCount=0])
2017-02-05T22:54:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=17, messageCount=0])
我不太确定发生了什么，但是有人可以告诉我是否应该为此担心吗？这是 RabbitMQ 还是 Spring XD 本身的问题？
谢谢。
这意味着您的模块之一未能处理消息 - 您应该在日志中看到其他信息（堆栈跟踪）。
你肯定用的是当前版本(1.3.1)；我有一个模糊的记忆，旧版本没有记录堆栈跟踪，这提供了失败的原因。
我有一个 Spring XD 1.2.0 安装，其中一台服务器和几个使用 RabbitMQ 作为消息总线的容器，我在日志中看到很多 WARN 消息，例如：
2017-02-05T22:51:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=14, messageCount=0])
2017-02-05T22:52:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=15, messageCount=0])
2017-02-05T22:53:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=16, messageCount=0])
2017-02-05T22:54:03+0100 1.2.0.RELEASE WARN xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1-1 retry.RejectAndDontRequeueRecoverer - Retries exhausted for message (Body:'Sent RUNNING to notification URL: http://doopex-back2:5002/services/data-project/project/5745722984ae22d0317b6377/http/5745743700b0b2c 10ca5494d/execution?action=RUNNING'MessageProperties [headers={contentType=text/plain}, timestamp=null, messageId=null, userId=null, appId=null, clusterId=null, ty pe=null, correlationId=null, replyTo=null, contentType=text/plain, contentEncoding=null, contentLength=0, deliveryMode=null, expiration=null, priority=0, redeliver ed=false, receivedExchange=, receivedRoutingKey=xdbus.s5745722984ae22d0317b6377-8ef5f339-f901-4c95-ae11-111be263ce82.1, deliveryTag=17, messageCount=0])
我不太确定发生了什么，但是有人可以告诉我是否应该为此担心吗？这是 RabbitMQ 还是 Spring XD 本身的问题？
谢谢。
这意味着您的模块之一未能处理消息 - 您应该在日志中看到其他信息（堆栈跟踪）。
你肯定用的是当前版本(1.3.1)；我有一个模糊的记忆，旧版本没有记录堆栈跟踪，这提供了失败的原因。