That was the big perf boost

On Wed, Oct 21, 2009 at 6:58 PM, Ayende Rahien <[email protected]> wrote:

> Yes, this is fixed.
>
>
> On Wed, Oct 21, 2009 at 6:56 PM, Steve Wagner <[email protected]> wrote:
>
>>
>> Now where you work on Rhino Queues i want to remind you on this issue :-)
>>
>> ------------------------------
>>
>> Ive created two simple command line applications to test how RSB works.
>> App 1 sends a simply message to app 2, so not complicated. The reason
>> for that mail is what app 2, which received the messages, outputs at
>> startup when i restart the application after all messages where handled.
>>
>> RSB: Scanning incoming message
>> 95514ec0-36af-42ba-9951-9ada5a105202/3a54c5f7-54c7-4966-a99e-9c73009293c0
>> on 'test2/' with status Processing
>> RSB: Scanning incoming message
>> 95514ec0-36af-42ba-9951-9ada5a105202/ea075fcb-0082-4cd1-a648-9c73009293cc
>> on 'test2/' with status Processing
>> RSB: Scanning incoming message
>> 95514ec0-36af-42ba-9951-9ada5a105202/d83a92df-e153-497c-a1d2-9c73009293d3
>> on 'test2/' with status Processing
>> ...
>>
>> All messages are processed and ComsumerOf are called before i restarted
>> the app, so why the message status is still Processing?
>>
>> -----------------------------
>>
>> -Steve
>>
>> Ayende Rahien schrieb:
>> > No, it most definitely should not. That is done on another thread, and
>> is
>> > completely async from the send op.
>> >
>> > On Wed, Oct 21, 2009 at 3:01 PM, Corey Kaylor <[email protected]>
>> wrote:
>> >
>> >> I believe the Dispose call  for TransactionScope is blocking until the
>> send
>> >> is complete.
>> >>
>> >
>> > >
>> >
>>
>> >>
>>
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to