Are you executing a $dhh->disconnect after you're done with using the db?
I would suggest running your script using the debugger to find out where it is hanging up.
from the command line:
perl -wd script_name.cgi
If you have query string parameters you can send them in as command line args:
perl -wd script_name.cgi name=value name2=value
The n key will step thru your program line by line, s will step into a subroutine. You should easily be able to find the line causing the problem that way. Check the docs for the debugger, it's the way to go.
hth,
john
| [reply] |
Yes, I'm using $dbh->disconnect, which is returning 1. I've tried running the script from the server and it executes fine and the process terminates like it should. It's only giving me a problem when IIS is running the process. Does anyone have any idea what this might be?
| [reply] |
Another new development... When I switch the server to use perlis.dll rather than perl.exe to handle perl scripts, it terminates correctly just as it does when run from a command line on the server.
However, I can't use perlis.dll because ISAPI doesn't pass enough information to my scripts as CGI does($ENV{'REMOTE_USER'} is critical to me). Anyone have any ideas based on this new information?
Another thing worth noting is that this does not happen all the time, just most of the time. About 20% of the time the process will terminate normally, it's the other 80% that it hangs. It's not spiking the CPU on the server, the process just hangs there using 0% CPU until the server timeout hits. | [reply] |