H
harini.gopi
Hi,
I have a CGI script wrapped as an exe running on IIS 6.0. It needs to
parse a 31MB file located on a NFS and redirect the output to another
CGI script for plotting. It works fine when the file size (that needs
to be parsed) is smaller but for larger files it just ends abruptly
without further processing. I understand that this could be because
the connection timeout for CGI scripts on IIS 6.0 is set to 300 s. But
there is no GUI in the IIS properties to edit the same. Can someone
guide me to edit the metabase file (IIS 6.0) for increasing the
connection timeout ?Also is this the right approach? Would there be an
alternate way to prevent the timeout from happening without having to
modify the IIS setting?
I should also add that the script executes fine when it is not
converted to an exe (conversion done via perl2exe) i.e when it remains
a stand alone ".pl" program. Does the wrapping into an exe cause any
other overhead that it forces a timeout?
Any reply would be appreciated.
Thanks,
Harini
I have a CGI script wrapped as an exe running on IIS 6.0. It needs to
parse a 31MB file located on a NFS and redirect the output to another
CGI script for plotting. It works fine when the file size (that needs
to be parsed) is smaller but for larger files it just ends abruptly
without further processing. I understand that this could be because
the connection timeout for CGI scripts on IIS 6.0 is set to 300 s. But
there is no GUI in the IIS properties to edit the same. Can someone
guide me to edit the metabase file (IIS 6.0) for increasing the
connection timeout ?Also is this the right approach? Would there be an
alternate way to prevent the timeout from happening without having to
modify the IIS setting?
I should also add that the script executes fine when it is not
converted to an exe (conversion done via perl2exe) i.e when it remains
a stand alone ".pl" program. Does the wrapping into an exe cause any
other overhead that it forces a timeout?
Any reply would be appreciated.
Thanks,
Harini