in reply to Re^2: Trapping Network errors in SOAP::Lite
in thread Trapping Network errors in SOAP::Lite

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?

  • Comment on Re^3: Trapping Network errors in SOAP::Lite

Replies are listed 'Best First'.
Re^4: Trapping Network errors in SOAP::Lite
by shreya (Novice) on Nov 01, 2006 at 22:11 UTC
    I am positive that it was during tranmission that my program crashed. How do I know this ? I tested it with our systems guy asking him to shut down the server while I was messaging it. Isin't eval suppose to be helpful here ? Any idea on why eval is not working her ?
[reply]

In Section Seekers of Perl Wisdom