NServiceBus 重试延迟 [英] NServiceBus Retry Delay

问题描述

配置/编码 NServiceBus 以延迟重试消息的最佳方法是什么?

What is the optimal way to configure/code NServiceBus to delay retrying messages?

在其默认配置中，重试几乎立即发生，直至达到配置文件中定义的尝试次数.理想情况下，我希望在一小时后重试，等等.

In its default configuration retry happens almost immediately up to the number of attempts defined in the configuration file. I'd ideally like to retry again after an hour, etc.

另外，HandleCurrentMessageLater() 是如何工作的?Later 方面指的是什么?

Also, how does HandleCurrentMessageLater() work? What does the Later aspect refer to?

推荐答案

NSB 重试是为了解决死锁等临时问题.通过创建另一个监控错误队列并将它们放回您喜欢的时间间隔的源队列.看看 NSB 自带的 ReturnToSourceQueue.exe 以供参考.

The NSB retries is there to remedy temporary problems like deadlocks etc. Longer retries is better handled by creating another process that monitors the error queue and puts them back into to the source queue at the interval you like. Take a look at the ReturnToSourceQueue.exe that comes with NSB for reference.

NServiceBus 现在支持这个，我们称之为二级重试，请参阅http://docs.particular.net/了解更多详情

NServiceBus now supports this , we call it Second Level Retries, see http://docs.particular.net/ for more details

这篇关于NServiceBus 重试延迟的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！