Hi, Thanks for digging into this.
It makes sense to remove the executor ID in this case. I'll put it on the maintenance list and will probably have a fix soon. Regards, Tibor > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:alchemi- > [EMAIL PROTECTED] On Behalf Of Reece Arnott > Sent: Sunday, May 28, 2006 10:28 PM > To: [email protected] > Subject: Re: [Alchemi-developers] Problem re-scheduling threads (Alchemi > 1.0.4 .Net 1.1) > > At 10:21 a.m. 29/05/2006, Reece Arnott wrote: > >Found the issue. When a thread is rescheduled, the executor ID is left > set > >so the thread cannot run until the executor it was running on comes back > >up. Presumably this executorID should be blanked out so it can run on > the > >next available executor. > > I've had a look and the part where the executor Id is reset and it is in > the the Reset method of Alchemi.Manage.MThread (should be called from > Alchemi.Manager.ManagerContainer.ScheduleDedicated() when there is a > problem executing the thread). > > In this method the Executor Id is reset to null and the time reset methods > called. As the time resets seem to be working I think the first thing to > check is whether that null (and any subsequent tests for it) should > actually be an empty string "". According to the .Net docs I've read that > shouldn't be a problem but I've had a lot of weirdness over the years > caused by null logic esp. on database assignments/queries. > > > > ------------------------- > Reece Arnott > Learning Environments Specialist > School of Business > University of Otago > Dunedin > New Zealand > > [EMAIL PROTECTED] > ------------------------- > > > > _______________________________________________ > Alchemi-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/alchemi-developers _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
