To fix the issue you can do This can be reverse-engineered somewhat from the SSCLI20 source, albeit that it is dated. The core CLR function that implements MsgWaitForMultipleHandles is DoAppropriateWait. From what I see, it is used by AutoResetEvent, ManualResetEvent and Semaphore but not by Mutex. One quirk is that WaitHandle.WaitAny is okay from an STA thread but WaitAll() generates an exception. Yeah, this isn't documented anywhere other then a few hints in Chris Brumme's blog. You can't assume too much from what I found, test this to be sure.
Rails 3 - Handle Incoming Messages (Allowing Users to reply to email notifications)
Hope that helps Yes, generally you would pass a callback into whatever function you have this in, and when 'end' is emitted, you should take the data that you collected in the request, and pass it to your callback. I realize it's pseudocode and you may know, I just want to say it anyways. Remember that 'data' can be called more than once, and that 'return' in your end function won't do anything.
Mule request-reply consuming all the messages in the JMS reply queue
hop of those help? In Mule Request-Reply pattern, JMS inbound endpoint is consuming all the messages in the queue. how can i avoid this behavior of mule. here is my flow , Try using a selector on the JMS inbound endpoint: