sigh, Thanks. I thought I had tests that covered the error actions. What is the scenario in which you are seeing this?
On Mon, Apr 13, 2009 at 11:06 PM, Corey Kaylor <[email protected]> wrote: > I've run into a condition that send us into an infinite error loop. > > The logic for the ErrorAction to work correctly depends on the call to > messageRecieved.GetInvocationList() in TransportUtil to always return the > ErrorAction's subscription first, which it doesn't. The invocation list will > return the methods in order that they are added by default, which in this > case is the DefaultServiceBus, then the ErrorAction. Resulting in > continually reading the same message from the queue over and over and never > gets moved to the error queue. > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
