http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Rishi, You cannot send a message to someone without being part of a transaction. http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment6http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment6Mon, 19 Jan 2009 13:41:35 GMTWould the roll back be per handler or all handlers? And if it is for all handlers, what if one handler did say shoot a message to some other service or write to a file without being part of the transaction, how would the roll-back be applicable? http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment5http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment5Mon, 19 Jan 2009 13:37:37 GMTRishi, Actually no, failure to process a message would cause the full action to be rolled back. http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment4http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment4Mon, 19 Jan 2009 12:40:28 GMTI just wanted to confirm given the retrying mechanism in RSB and the concurrency issues you've mentioned here, we need to design the consumers to be idempotent through-and-through? http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment3http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment3Mon, 19 Jan 2009 08:23:00 GMTthanks, fixed http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment2http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment2Mon, 19 Jan 2009 05:14:47 GMTYou have an indentation problem in this post, where you don't break back out when you are done quoting Jason's point. http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment1http://ayende.com/3822/rhino-service-bus-concurrency-in-a-distributed-world#comment1Mon, 19 Jan 2009 04:54:58 GMT