Problem 1 -- apache cgi problem
We have a problem with Apache 2.0.43 on Win32 (Windows 2000 server). We
are using SOAP-LITE.pm (version 0.55, though the revision doesn't seem
to matter) to send information back and forth between our server and
client browsers (using regular CGI, not mod-perl). The SOAP is being
sent via HTTP over port 80. (The browsers are IE 6.0 using
Apache-XML-Java-SOAP but this also seems to be irrelevant to the
problem.) The problem seems to be that any time another CGI process
starts, the client browsers receive a "socket closed by host" message.
The conflicting CGI can either be another SOAP cgi or any other kind of
CGI. After the conflicting CGI quits, communication with the SOAP CGI
resumes (forcing the conflicting CGI to take a long time causes a
corresponding delay in the resumed communication). This problem did not
occur using Apache 1.something on Windows NT 4.0 server (there were
other, serious, problems that have been addressed by upgrading to 2.0.43
We have a problem with Apache 2.0.43 on Win32 (Windows 2000 server). We
are using SOAP-LITE.pm (version 0.55, though the revision doesn't seem
to matter) to send information back and forth between our server and
client browsers (using regular CGI, not mod-perl). The SOAP is being
sent via HTTP over port 80. (The browsers are IE 6.0 using
Apache-XML-Java-SOAP but this also seems to be irrelevant to the
problem.) The problem seems to be that any time another CGI process
starts, the client browsers receive a "socket closed by host" message.
The conflicting CGI can either be another SOAP cgi or any other kind of
CGI. After the conflicting CGI quits, communication with the SOAP CGI
resumes (forcing the conflicting CGI to take a long time causes a
corresponding delay in the resumed communication). This problem did not
occur using Apache 1.something on Windows NT 4.0 server (there were
other, serious, problems that have been addressed by upgrading to 2.0.43