Here's what I do:

    $soap->on_fault(
        sub {
            my ( $soap, $res ) = @_;

            if ($res) {
                if ( ref $res ) {
                    die join( '; ', $res->faultcode, $res->faultstring
+, $res->faultdetail ) . "\n";
                }
                else {
                    die $res;
                }
            }
            else {
                die "Soap Fault: " . $soap->transport->status . "\n";
            }
        } );
[download]

Then later in the client...

eval {
    $soap->Method("arguments");
};

if ($@) {
    // provide some user feedback about the error in $@
}
[download]

SOAP::LITE is single threaded ???
If it is true then how to change it to multiple?

It can help me to save my client if my service server dies ...

Please Help ...

create a new soap lite object in each subthread

The RPC::Any package-family has an interesting approach to a similar problem.   The outer-level server framework wraps the handler-routines in an exception-handling block, and it also defines a set of structured error classes.   If any handler encounters either an impossible situation or a bug, it throws an exception.   The exception is caught and an error-response is returned.   Because of the fact that you can throw objects, not just strings, the response can be quite customized because the “catcher” has more than just a string to work with.   You might want to take a look at what they did as a source of good ideas.   Also Exception::Class.   It worked really well for me ... came out very clean and straightforward.