On Sun, Jul 5, 2009 at 6:13 PM, Francesco Petrarch <f_petra...@hotmail.com>wrote:
> It's been awhile since I have looked into this and I think I have tracked > it down. In short, I now believe that ns_adp_abort aborts all current > threads/adps, not just the one currently executing the ns_adp_abort line. > Therefore, when these "blank screens" were appearing on my site to VISITOR A > it was because another visitor (VISITOR B) had visited a page which called > ns_adp_abort (for example after a ns_returnredirect) before the VISITOR A > thread finished. > > Does that make sense? Can someone with more experience in the code take a > look and let me know? > No, makes no sense. This is essentially impossible. Each thread executes pretty much independently of all others. The problem probably has to do with the adp configuration...error without signaling an error, which is a configuration which is necessary to keep complex sites up if one component is not working. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <lists...@listserv.aol.com> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
