I've been running 2.0.36 on a Windows 2000 box for some time now, using is to service SOAP requests using the ISAPI version of the Microsoft SOAP Toolkit 2.0. Everything was actually working great, until I put in 2.0.39 this morning. Now, none of my SOAP calls (HTTP POST) work anymore. In fact, in some cases, Apache itself crashes and burns -- restarting itself. I haven't built anything, I'm simply running with the Win32 Apache binaries. The only real new warning/error message I've seen is this: [Wed Jun 19 10:36:50 2002] [warn] [client 192.168.1.3] ISAPI: asynch I/O result HSE_STATUS_PENDING from HttpExtensionProc() is not supported: C:/Program Files/Common Files/MSSoap/Binaries/SOAPISAP.dll I never saw this warning under 2.0.36. I did see that there were extensive changes made to ISAPI support in 2.0.37, so I suspect something has changed that breaks the 2.0.36 functionality that I was using.
Try the as-yet-undocumented directive ISAPIFakeAsync on in order to support a pseudo-async behavior. Badly written isapi modules could consume a worker thread forever, without timing out, so it isn't idea just yet. But please reply if this solves the bug and gets your SOAP .dll working again.
Thanks for your help. Yes, the "ISAPIFakeAsync on" appears to have solved my problem, although I have some additional stress testing I want to do. My question at this point is should I go ahead and use this un-documented directive now in a production environment with 2.0.39, or is it safer to wait for an upcoming build where this has had some time to stabalize? I know that's probably not a fair question, but I'm looking for your opinion on the relative stablity of the rewritten mod_isapi in 2.0.39. Thanks again for your help.
That your module worked before was a happy accedent :-) Yes, after sufficient stress testing, it is vastly preferable to use the Apache 2.0.39 version of mod_isapi than any prior version (including 1.3). Of course I cannot stress the mod_isapi in every way that it will be used by isapi extension authors. That is what field testing is all about. I'm glad to hear of your success, and expect that mod_isapi has sufficiently stabilize to use in production, with proper monitoring. Of course there are no warrenties... if it breaks, you get to keep both pieces :-)