You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/07/02 16:33:52 UTC
DO NOT REPLY [Bug 10408] New: -
ISAPI issue with 2.0.39 for Win32
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10408>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10408
ISAPI issue with 2.0.39 for Win32
Summary: ISAPI issue with 2.0.39 for Win32
Product: Apache httpd-2.0
Version: 2.0.39
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: mod_isapi
AssignedTo: bugs@httpd.apache.org
ReportedBy: bbukovics@radiantsystems.com
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org