http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Steve, I intend to do so, but I am trying to juggle quite a few balls at the moment. It will get there, but it will take time http://ayende.com/3791/errors-are-part-of-your-experience#comment6http://ayende.com/3791/errors-are-part-of-your-experience#comment6Sat, 03 Jan 2009 20:35:57 GMTDemis, Absolutely. I was able to replay all failed transactions! http://ayende.com/3791/errors-are-part-of-your-experience#comment5http://ayende.com/3791/errors-are-part-of-your-experience#comment5Sat, 03 Jan 2009 20:32:36 GMTJason, No, I am not. A failure is a failure is a failure. It depends on the semantics of the app to decide what to do with it. Rhino Service Bus simply make sure that the information is accessible and easy to view. http://ayende.com/3791/errors-are-part-of-your-experience#comment4http://ayende.com/3791/errors-are-part-of-your-experience#comment4Sat, 03 Jan 2009 20:30:43 GMTI hope to see you continue to update the Rhino Service Bus and it's sample (dummies like me need samples... lol) - it's a great setup and I'm looking forward to adding this capability into my applications http://ayende.com/3791/errors-are-part-of-your-experience#comment3http://ayende.com/3791/errors-are-part-of-your-experience#comment3Sat, 03 Jan 2009 16:09:23 GMTI've been using ActiveMQ for some time now to store error requests as well. I wrap them up in a SOAP Fault storing details about the error as well as the 'error request'. The benefit of using MQ's for error handling is that you can deal with your errors programmatically, i.e. once you have fixed the bug that caused the error you can replay the 'error request' to ensure it works and if its a 'Store Message' its still processed (i.e. Store and forward) so you don't lose any important messages. http://ayende.com/3791/errors-are-part-of-your-experience#comment2http://ayende.com/3791/errors-are-part-of-your-experience#comment2Sat, 03 Jan 2009 14:25:02 GMTIn the past I've used log4net for logging, which works OK. But log files often have a way of becoming burdensome to wade through, so more often than not important errors are not seen. This is definitely an interesting take on the idea of logging. Are you (or have you thought about) using message priority to represent the error severity so that more critical errors bubble to the top? http://ayende.com/3791/errors-are-part-of-your-experience#comment1http://ayende.com/3791/errors-are-part-of-your-experience#comment1Sat, 03 Jan 2009 13:56:46 GMT