Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
go ahead... be a heretic
 
PerlMonks  

Re: Handle application errors with mod_perl

by sundialsvc4 (Monsignor)
on Feb 07, 2013 at 20:58 UTC ( #1017725=note: print w/ replies, xml ) Need Help??


in reply to Handle application errors with mod_perl

Gentlebeings ... a moment’s respectful pause, I beseech thee ...

The root cause of the problem, with respect to this mod_perl-based application, is not that a misfortunate error occurred ... but that the consequence of that error, when it misfortunately occurred, was that the exception blew all the way out to “Apache, itself.”   Any self-respecting web application, in whatever implementation-language it might be, must be able to keep up a good face in front of its audience while the show is going on, no matter what sort of calamity is happening backstage.

“Ladies and Gentlemen, good evening.   I’m very sorry, but the entire back-half of the theater has just been consumed by an unanticipated thermonuclear fusion reaction.   Will you please now gather your coats and exit through the doorways to the left or to the right.   You may exchange your tickets for a full refund at the box-office tomorrow morning if the aforesaid box office is still here.   Thank you, and good night.”   Grace under pressure.

“SQL errors,” (will surprises never cease??) ... guess what ... sh*t happens.   Just like any other sh*t that “could happen.”   But the bottom line is ... no matter what happens, you gotta save face in front of the customer.

Ergo:   you must, above all else, ensure that there is “an exception-handler of last resort.”   And, having built that, you must likewise ensure that it does something reasonable.   Hand the doomed customer a free drink along with his life-jacket.   But don’t, whatever you do, actually let the airplane hit the ground.   That’s not “Perl” ... that’s not even “web.”   That’s just common sense.

The second point, likewise, is “just common sense.”   If the theater that you are running has just experienced a thermonuclear meltdown, for reasons that you particularly know not, then it just might be prudent to commit suicide, so that the operating system will obliterate all the wreckage.   Apache, in its turn, will then spawn a brand new clean-slate.

Hey ... if that “bothers you,” then with my blessings please down-vote this response to your heart’s content and have a wonderfully nice day.


Comment on Re: Handle application errors with mod_perl
Re^2: Handle application errors with mod_perl
by SuicideJunkie (Priest) on Feb 07, 2013 at 22:16 UTC
    But the bottom line is ... no matter what happens, you gotta save face in front of the customer.

    On a complete tangent over to human relations, that is the cause of a lot of headaches I hate. When you know there is a problem, and they just won't admit it. It makes the denier look bad, and problems don't get solved.

    Don't save face. After all, Step One is admitting that there is a problem.

      Acknowledge a problem exists, but pull your pants up :) C.Y.A - Cover Your A.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1017725]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (13)
As of 2014-04-24 12:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (565 votes), past polls