While Komodo is the best debugger I've ever used for Perl, it has been my experience that it will report "500 read timeout" HTTP responses when running Linux LWP or WWW::Mechanize scripts. If you run the same script from the command line, you will not see these problems (it just sucks to be you if you're trying to debug a problem that occurs somewhere after a few HTTP requests). This has been my experience for Komodo version 3.5 and 4.0. Let's hope the ActiveState team can fix this sometime soon, this is the only fault I can find in their otherwise *excellent* tool.

In reply to Re^2: LWP error 500 read timeout "internal response" by Anonymous Monk
in thread LWP error 500 read timeout "internal response" by cormanaz

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.