The one thing to be careful with is that when you do that, the original message ID is lost.
This becomes significant if the server to which you're replaying the message needs to reply to a client (or some other server) which is going to be using that original ID for the purpose of correlation. When a message is moved to the error queue in NServiceBus, we attach a header including the original message ID, and then when the message arrives back at the server, the infrastructure uses the information in that header as the message's ID instead of the one from MSMQ. Cheers, -- Udi Dahan From: [email protected] [mailto:[email protected]] On Behalf Of Sebastien Crocquesel Sent: Monday, June 07, 2010 5:33 AM To: [email protected] Subject: Re: [rhino-tools-dev] How do I replay errors? Also, the windows MSMQ console allow you to do that also. right on a message, move and select the destination queues. The drawback is that it's a single only message operation which can be tedious if you have a lot of errors. 2010/5/26 Ayende Rahien <[email protected]> You either write a script or use the GUI tools (I use http://www.cogin.com/mq/) to move the messages from the error queue to the main queue. That is all On Wed, May 26, 2010 at 4:43 AM, Nathan Palmer <[email protected]> wrote: I'm testing Rhino ESB to find out which service bus is going to work for me. What I'm trying to find out is how we will handle errors. I have created a solution that throws errors and now everything has moved to the error queue. What I would like to do is move the errors back into the regular queue, fix the exception and then start the process back up. According to Ayende's blog post here they can be "replayed" http://ayende.com/Blog/archive/2009/01/03/errors-are-part-of-your-experience .aspx How do I go about doing this? Thanks, Nathan Palmer -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:rhino-tools-dev%[email protected]> . For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected] <mailto:rhino-tools-dev%[email protected]> . For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
