Masstransit error queue is consuming, but still is not empty

Question

I am using Mastransit 3.5.0 with RabbitMq. If queue consumers throws exception, its is handled by default MoveExceptionToTransportFilter and moved to _error queue. For _error queue I have seperate consumer: Consume(ConsumeContext> context)

Behavior of Fault is rather different. Part of errors are handled and removed from _error queue, but part of error message still remain in error queue and do not consumed by this consumer. As I understand If I have Fault consumer then _error queue should be empty.

I can not find explanation, why errors are still in queue. Maybe because these faults were once consumed, but I cant find any indication in the headers or else where?

score 5 · Accepted Answer · answered Sep 09 '17 at 08:49

5

This is not correct.

You should not consume from the error queue. Error queue accumulates messages that crashed their consumers, for diagnostics purposes.
Faut<T> messages are published in addition to moving messages to the error queue. These two things are unrelated.
If you have a consumer of Fault or Fault<T> events, you just do that - consume these events. It has nothing to do with messages in the error queue.

answered Sep 09 '17 at 08:49

Alexey Zimarev

17,944
2
55
83

Is there no way to properly consume the error queue, say in a second time, once the receiving hand has been corrected ? – Romain Vergnory Jul 09 '19 at 10:24
1

You can use the Shovel plugin to move messages from the error queue back to the normal queue. – Alexey Zimarev Jul 09 '19 at 16:06
@AlexeyZimarev This answer should be in the MassTransit docs. None of this is obvious to a first-time user. – Robotronx May 21 '21 at 10:26

Masstransit error queue is consuming, but still is not empty

1 Answers1

Linked