EasyNetQ - 如何在 EasyNetQ_Default_Error_Queue 消息中包含原始队列名称?

EasyNetQ - how can I include the original queue name in the EasyNetQ_Default_Error_Queue message?

当使用 Publisher/Subscriber 模式并且在订阅者处理期间抛出异常时,EasyNetQ 默认将消息放入 EasyNetQ_Default_Error_Queue.

问题是错误消息中只有原始交易所名称。我真正需要的是原始队列名称,这样我就可以将消息重新发布到队列,而不是交换器。

如何在错误消息中包含队列名称?

EasyNetQ_Default_Error_Queue 中的示例错误消息:

{
   "RoutingKey": "",
   "Exchange": "EiHD.Application.Restaurant.Events.RestaurantDeliveryMailChanged:EiHD",
   "Exception": "System.AggregateException: Um ou mais erros. ---> System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto.\r\n   em EiHD.Infrastructure.Mailing.EmailSender.OnEvent(RestaurantDeliveryMailChanged evt) na d:\Projetos\EatInHouseDelivery\sln\Infrastructure\Mailing\EmailSender.cs:linha 136\r\n   em EiHD.Infrastructure.EventDispatching.EasyNeqQEventDispatcher.<>c__DisplayClass5`1.<RegisterListener>b__4(T evt) na d:\Projetos\EatInHouseDelivery\sln\Infrastructure\EventDispatching\EasyNeqQEventDispatcher.cs:linha 68\r\n   em EasyNetQ.RabbitBus.<>c__DisplayClass6`1.<Subscribe>b__5(T msg)\r\n   --- Fim do rastreamento de pilha de exceções internas ---\r\n---> (Exceção Interna N° 0) System.NullReferenceException: Referência de objeto não definida para uma instância de um objeto.\r\n   em EiHD.Infrastructure.Mailing.EmailSender.OnEvent(RestaurantDeliveryMailChanged evt) na d:\Projetos\EatInHouseDelivery\sln\Infrastructure\Mailing\EmailSender.cs:linha 136\r\n   em EiHD.Infrastructure.EventDispatching.EasyNeqQEventDispatcher.<>c__DisplayClass5`1.<RegisterListener>b__4(T evt) na d:\Projetos\EatInHouseDelivery\sln\Infrastructure\EventDispatching\EasyNeqQEventDispatcher.cs:linha 68\r\n   em EasyNetQ.RabbitBus.<>c__DisplayClass6`1.<Subscribe>b__5(T msg)<---\r\n",
   "Message": "{\"FromEmail\":\"someemail@gmail.com\",\"ToEmail\":\"anotheremail@gmail.com\",\"RestaurantName\":\"SomeRestaurant\"}",
   "DateTime": "2015-10-25T19:20:17.2317949Z",
   "BasicProperties": {
      "ContentType": null,
      "ContentEncoding": null,
      "Headers": {},
      "DeliveryMode": 2,
      "Priority": 0,
      "CorrelationId": "f212f734-6cd7-41fe-ac71-09335f44bb2c",
      "ReplyTo": null,
      "Expiration": null,
      "MessageId": null,
      "Timestamp": 0,
      "Type": "EiHD.Application.Restaurant.Events.RestaurantDeliveryMailChanged:EiHD",
      "UserId": null,
      "AppId": null,
      "ClusterId": null,
      "ContentTypePresent": false,
      "ContentEncodingPresent": false,
      "HeadersPresent": true,
      "DeliveryModePresent": true,
      "PriorityPresent": false,
      "CorrelationIdPresent": true,
      "ReplyToPresent": false,
      "ExpirationPresent": false,
      "MessageIdPresent": false,
      "TimestampPresent": false,
      "TypePresent": true,
      "UserIdPresent": false,
      "AppIdPresent": false,
      "ClusterIdPresent": false
   }
}

我找到了解决办法。

我必须将 DefaultConsumerErrorStrategy class 的扩展版本注册到我的总线的 IConsumerErrorStrategy:

this.bus = RabbitHutch.CreateBus(this.connectionString, (serviceRegister) => {
    serviceRegister.Register<IConsumerErrorStrategy>((sp) => new ExtendedConsumerErrorStrategy(sp.Resolve<IConnectionFactory>(), sp.Resolve<ISerializer>(), sp.Resolve<IEasyNetQLogger>(), sp.Resolve<IConventions>(), sp.Resolve<ITypeNameSerializer>()));
});

public class ExtendedConsumerErrorStrategy : DefaultConsumerErrorStrategy
{
    public ExtendedConsumerErrorStrategy(IConnectionFactory connectionFactory, ISerializer serializer, IEasyNetQLogger logger, IConventions conventions, ITypeNameSerializer typeNameSerializer)
        : base(connectionFactory, serializer, logger, conventions, typeNameSerializer)
    {   
    }

    public override AckStrategy HandleConsumerError(ConsumerExecutionContext context, Exception exception)
    {
        context.Properties.Headers.Add("OriginalQueue", context.Info.Queue);
        return base.HandleConsumerError(context, exception);
    }
}

现在我的消息中有了原来的 queue 名字 Headers 属性。适合我。