I guess it's possible that it was thrown in such a way that SOAP::Lite did/could not catch it -- after all, as you said, it caused the program to die horribly.

Typically with SOAP, transport errors include things such as HTTP errors, or the server not being available for whatever reason. So, by setting on_fault to an empty subroutine, you're suppressing most (maybe not all) transport errors.

That being said -- are you sure that the SOAP call is what caused the program to crash? Could there have been something else in your program that did it? Can you duplicate the problem, and/or trace it to a specific section of code?


In reply to Re^3: Trapping Network errors in SOAP::Lite by jhourcle
in thread Trapping Network errors in SOAP::Lite by shreya

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.