You could add code to all of your error trapping that specifically traps
database errors. Then in the handling for that check for the existence
of a application or server scope (depending on how many applications you
have on the server) variable like say "server.dberrorReported." If it
does not exist or is false, send the email and set
"server.dberrorReported" to true. If "server.dberrorReported" is true,
than just log the error. You would then have to remember to reset the
variable to false when the problem is over.
There are caveats to using the server scope. Which I'm sure people will
chime in about.
I would also recommend trying to go after the underlying issue. If
losing your database server and generating enough errors to clogs your
mailserver, is happening frequently enough to cause you to try and
change your error handling techniques, you may need to re-evaluate your
configuration, hardware or networking.
Terrence Ryan
Senior Systems Programmer
Wharton Computing and Information Technology
E-mail: [EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four
times a year.
http://www.fusionauthority.com/quarterly
Archive:
http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246769
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
