在Azure中NServiceBus错误队列 [英] NServiceBus error queues in Azure

问题描述

我试图安装NServiceBus在Azure上。在地方发展我使用的存储器队列，并在云中部署时，我使用Azure的服务总线。对于当错误发生时某些原因，消息不会移动到错误队列。事实上，错误队列甚至没有创造。

I'm trying to setup NServiceBus in Azure. During local development I am using the storages queues and when deployed in the cloud I am using the Azure Service Bus. For some reason when an error occurs, messages are not moved to the error queue. In fact, the error queue isn't even created.

在我的Web.config文件中，我有以下配置：

In my Web.config file I have the following configuration:

<MessageForwardingInCaseOfFaultConfig ErrorQueue="myApp-errors"/>

在配置NServiceBus我打电话：

When configuring NServiceBus I call:

.MessageForwardingInCaseOfFault()

当消息出现故障时，日志中的最后一个错误是总是

When a message fails, the last error in the log is always

Failed raising 'transport message received' event for message with ID=170ad256-b559-417e-8b34-3882045cc19e

在这个有什么想法？消息似乎工作，它只是错误处理不起作用。

Any thoughts on this? Messaging seems to work, it's just the error handling that doesn't work.

推荐答案

我的第一个猜测是，在名称captials不准错误队列不能创建

My first guess is that the error queue can not be created as captials in the name are not allowed

如果不行，我们必须做的更彻底ananlysis，但这需要从日志中一点点的更多信息。

If that doesn't work, we'll have to do a more thorough ananlysis, but that would require a little more information from the logs.

希望这有助于

这篇关于在Azure中NServiceBus错误队列的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！