Thanks Corey, I know this is not a normal behavior but we found that, due to some problems in our database, we had more than 40,000 messages in our MSMQ.
I had to create a new MSMQ queue to be used in our system and keep all other messages in the original one to be consumed by another process. The original queue had the "starter messages" at the end, but the messages created from our other systems where consumed in the new queue. When the other process consumed all original queue messages, the saga exists and the ESB could process many of the discarded messages in the new queue. By now I have a process that reads directly the discarded messages from queue with System.Messaging.MessageQueue and then using an IOneWayBus I move those existent messages as "new messages". My question was intended trying to know if Rhino Service Bus includes something to "Retry discarded message" On Wed, Jan 5, 2011 at 12:19 PM, Corey Kaylor <[email protected]> wrote: > Being moved to the discarded queue means there were no consumers consuming > that message. In the case of Saga's it means that the saga was already > completed, never started, or has a mismatched CorrelationId. I can't think > of why it would keep moving to the discarded queue other than the reasons > I've mentioned. > > -- > 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]<rhino-tools-dev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > -- Fernandojosé Boiton http://www.fboiton.com/ -- 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.
