Thanks for that!

On Sun, May 10, 2009 at 12:45 AM, Mike Nichols <[email protected]>wrote:

>
> should be fixed now
>
> On May 9, 5:31 am, Ayende Rahien <[email protected]> wrote:
> > Okay committed, and I think that issue is fixed.There is now an issue
> with
> > failed tests because of a problem with a different app domain. I will be
> > grateful if someone can look this over a little closer
> >
> > On Sat, May 9, 2009 at 2:50 PM, Ayende Rahien <[email protected]> wrote:
> > > Okay, I think I found the problem. It is actually related to a bug in
> how
> > > we process dispose.Dispose will NOT complete before all the
> transactions
> > > run, but we set the wasDisposed flag before all transactions completed.
> >
> > > On Sat, May 9, 2009 at 2:21 PM, Ayende Rahien <[email protected]>
> wrote:
> >
> > >> Mike,Currently I am concentrating on getting the RQ tests to run
> > >> consistently.
> > >> I'll look into your finding once they do so.
> >
> > >> On Fri, May 8, 2009 at 9:16 PM, Mike Nichols <
> [email protected]>wrote:
> >
> > >>> he he...alright...can you just take a moment to read this? I am not
> > >>> sure if this is a hint on that ObjectDisposedException:
> > >>> Should_go_to_discard_sub_queue_and_be_able_to_restart_bus hangs
> > >>> frequently seemingly because the transaction is trying to commit
> after
> > >>> the transport was disposed (as well as the queue maanger).
> >
> > >>> According to the debug log during this test:
> > >>> Should_go_to_discard_sub_queue_and_be_able_to_restart_bus looks like
> > >>> the RQ transport is being disposed just after the call to Discard()
> is
> > >>> made and the transaction tries to complete after that. RQManager is
> > >>> complaining that there is an open transaction while disposing so I
> did
> > >>> this in RQTransport during ProcessMessage:
> > >>>                        if (TransportUtil.ProcessSingleMessage
> > >>> (currentMessageInformation, messageRecieved) == false)
> > >>>                        {
> > >>>                                tx.Dispose();
> > >>>                               tx = null;
> >
> > >>>  Discard(currentMessageInformation.Message);
> > >>>                        }
> >
> > >>> See that I am disposing the the transaction and nulling it so that
> the
> > >>> tx.Complete() call won't be made... I can debug again and again this
> > >>> test and not getting any ObjectDisposedExceptions but I am not sure
> > >>> this is legitimate or even makes sense.
> >
> > >>> The timing test, Can_send_timed_messages, fails sometimes and passes
> > >>> others...this is true without my change and I am getting a JET
> > >>> Currency exception about no current record.
> >
>

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