but well, you're definitely right, having a look at the error_log would be very helpful, so i am organizing to get access to them.I just showed you how to keep your own log, so you can pinpoint exactly which statement is causing your application to hang. In CGI enviroment, during development, you'll also want to redirect STDERR with CGI::Carp's carpout, like
CGI Help Guide (among others) in Tutorials for more tips.BEGIN { use CGI::Carp qw(carpout); open(LOG, ">>/usr/local/cgi-logs/mycgi-log") or die("Unable to open mycgi-log: $!\n"); carpout(LOG); }
do you say, the code is incomplete, becaus i did not post the rest of the script or because something is missing *at* the code i posted?I say its incomplete (even after your update) because Statements::doSelect and DBKomm::connectdb only exist on your computer.
If it is your database communication to blame, well, only you can help yourself. If you are using DBI ($sth is a hint that you may be, but I can't tell), I'd say make sure you RaiseError => 1 when you connect, and if that doesn't give you any insight, turn on trace (see DBI_TRACE in the DBI documentation), but like I said, I don't know what you're using.
In reply to Re^3: host does not respond; sometimes
by PodMaster
in thread host does not respond; sometimes
by zetetes
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |