We can tweak the log statement to make it easier to filter if that would help when it fit this type of scenario. Or log at a different level under that same condition.
On Thu, Mar 10, 2011 at 2:47 PM, Jason Meckley <[email protected]>wrote: > a logged error represents a problem. I don't want the admin to "just know" > that this is a false positive. The point at which is message is logged > doesn't leave room to determine if no consumer is OK or not. > > For now I removed the delayed message. If this was needed in the future i > would look into an NoOp Saga instead. > > -- > 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.
