Send to error queue without retry

[Geoff]

Is it possible to instruct MT to send a message to the error queue without further retry?

We have some messages that for various reasons are considered invalid and not suitable for retry.  Whilst we could just discard them I feel they belong in the actual error queue, since they are unprocessable to us and warrant additional investigation.

PS we are successfully running a high volume realtime data feed through RabbitMQ and MT in a clustered solution with great success. Thanks for the great support in this group and for building MT !

Thanks,

Geoff

[Chris Patterson]

There isn't surfaced way to do this automatically, but you could call bus.GetEndpoint(theUriOfYourErrorEndpoint).Send(...) to put it there.

I'll see if an extension method can be added to send it directly.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To post to this group, send email to masstrans...@googlegroups.com.
To unsubscribe from this group, send email to masstransit-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/masstransit-discuss/-/XAapHcpSj0IJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Geoff]

Thanks Chris - I like the extension idea - generating endpoint URI's doesn't particularly appeal :)

On Friday, August 31, 2012 12:29:39 PM UTC+10, Chris Patterson wrote:

There isn't surfaced way to do this automatically, but you could call bus.GetEndpoint(theUriOfYourErrorEndpoint).Send(...) to put it there.

I'll see if an extension method can be added to send it directly.

On Thu, Aug 30, 2012 at 7:00 PM, Geoff <ge...@geoffsteffens.com> wrote:

Is it possible to instruct MT to send a message to the error queue without further retry?

We have some messages that for various reasons are considered invalid and not suitable for retry.  Whilst we could just discard them I feel they belong in the actual error queue, since they are unprocessable to us and warrant additional investigation.

PS we are successfully running a high volume realtime data feed through RabbitMQ and MT in a clustered solution with great success. Thanks for the great support in this group and for building MT !

Thanks,

Geoff

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To post to this group, send email to masstrans...@googlegroups.com.

To unsubscribe from this group, send email to masstransit-discuss+unsub...@googlegroups.com.

[Brian Hanolt]

Did an extension ever get created for this?  Thanks.

On Thursday, August 30, 2012 10:29:39 PM UTC-4, Chris Patterson wrote:

There isn't surfaced way to do this automatically, but you could call bus.GetEndpoint(theUriOfYourErrorEndpoint).Send(...) to put it there.

I'll see if an extension method can be added to send it directly.

On Thu, Aug 30, 2012 at 7:00 PM, Geoff <ge...@geoffsteffens.com> wrote:

Is it possible to instruct MT to send a message to the error queue without further retry?

We have some messages that for various reasons are considered invalid and not suitable for retry.  Whilst we could just discard them I feel they belong in the actual error queue, since they are unprocessable to us and warrant additional investigation.

PS we are successfully running a high volume realtime data feed through RabbitMQ and MT in a clustered solution with great success. Thanks for the great support in this group and for building MT !

Thanks,

Geoff

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To post to this group, send email to masstrans...@googlegroups.com.

To unsubscribe from this group, send email to masstransit-discuss+unsub...@googlegroups.com.