|
I thought that the "Medium - Pooled" and "High -
Isolated" settings for websites in IIS5 effectively took care of the ISAPI
issues you indicated below.
On running PERL.EXE, let's talk about what happens
when someone launches nnn connects to your perl script. Got RAM?
:-).
The obvious solution is develop using perl.exe,
then use perlis for production. Which quite coincidentally is what I do
here :-).
Brian
----- Original Message -----
Sent: Sunday, August 10, 2003 12:39
Subject: RE: 502 error occurred in IIS
4.0
Only
a perfect coder should use ISAPI filters. If your perl process goes
nutty, haywire, or just plain rampant, then you have quite effectively brought
down the web-server.
It
is also a potential security flaw, ie above situation, but a bad guy decides
to overflow something, not the good guys like you and I :) Plus the
speed benefits are marginal. We're not talking P2-400's anymore, almost
every webserver is at least a dual p3-gigger..
How
about something simple like a database lock? ODBC Manager, by default
only allows 3 concurrent connections (i think) . And your ISP hoster
should have TCP timeouts on the server to drop connections, as well your perl
script should have a routeine to check the connection between itself and the
end-user.
MK
Why is he using perl.exe anyway? With IIS you
should use the Perl ISAPI (perlis.dll), not perl.exe, unless there is a
specific reason for having to use the latter.
In any case, I believe the 10 simultaneous
connection limit applies to Win2K pro and Win NT workstation, not Win2K
server or NT server.
Brian
----- Original Message -----
Sent: Thursday, August 07, 2003
16:27
Subject: RE: 502 error occurred in
IIS 4.0
I am not a IIS guru -- I prefer Apache; so take my research with a
grain of salt.
But that aside, I tried Google with the following
query:
IIS 10 simultaneous connections
perl
The groups is:
The web is:
The first link of both searches yield the answer. The IIS
only allows 10 simultaneous connections....I believe a search of this
list's archives will yield similar results.
Cheers,
Ward
Hi,
We are running IIS
4.0 Win NT 4.0 box with Perl 5.6 building 633, connect to Access data
file using ODBC.
The script is too large so
I split it into several smaller files and "require" used in the main
script file.
When a few clients connect to our web server, 502
error occurs. More than 10 instance of perl.exe sit in the memory and
http and ftp service is not accepting any request until the cgi
timeout(about 10 minutes).
We tried to duplicate the error but failed.
Initially our ISP blamed Perl script. When I request them to duplicate
the error and they failed also. Our ISP contacted Microsoft for trouble
shooting and got back to us with this:
MS has verified all possible
areas of IIS settings that would cause the timeout issue. At this time
no other variables are found and can be configured on IIS to prevent the
timeout issue. MS has analyzed and reviewed the provided IIS logs and
Perfmon files.
Please contact the Perl
software vendor for any assistances or work with the particular remote
users to troubleshoot the issues since only those particular users could
duplicate the issue.
It's mystery to me why the
error only happened to 4(I mean from 4 IP addresses) of them. It has
been a while since the problem occurred.
Any body had this kind of
problem?
Thank you very much.
Eric
The information contained in this message is intended
only for the recipient, and may be a confidential attorney-client
communication or may otherwise be privileged and confidential and
protected from disclosure. If the reader of this message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, please be aware that any
dissemination or copying of this communication is strictly prohibited.
If you have received this communication in error, please immediately
notify us by replying to the message and deleting it from your
computer.
Thank you,
Standard & Poor's
|
