Re: Trapping Network errors in SOAP::Lite

You should look at what 'on_fault' does:

on_fault()

This lets you specify a handler for on_fault event. The default behavior is to die on an transport error and to do nothing on other error conditions. You may change this behavior globally (see "DEFAULT SETTINGS") or locally, for a particular object.

So, by setting it to 'sub {}', you told it to ignore transport errors.

Comment on Re: Trapping Network errors in SOAP::Lite

Replies are listed 'Best First'.
Re^2: Trapping Network errors in SOAP::Lite by shreya (Novice) on Nov 01, 2006 at 21:51 UTC
By setting on_fault(sub{}) did not cause my program to ignore transport errors. My program crashed last week because when it was in middle of sending out a message the receiving server crashed. I thought setting on_fault (sub{}) would handle such issues but it apparently is not. Any advice ?	[reply]
Re^3: Trapping Network errors in SOAP::Lite by jhourcle (Prior) on Nov 01, 2006 at 22:03 UTC
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?	[reply]
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]