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
BEGIN { use CGI::Carp qw(carpout); open(LOG, ">>/usr/local/cgi-logs/mycgi-log") or die("Unable to open mycgi-log: $!\n"); carpout(LOG); }
CGI Help Guide (among others) in Tutorials for more tips.
 
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.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.


In reply to Re^3: host does not respond; sometimes by PodMaster
in thread host does not respond; sometimes by zetetes

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.