Thanks for the reply Matt. There are some useful nuggets of information the
site you provided.
Scott
On 7/17/06, Matt Robertson <[EMAIL PROTECTED]> wrote:
>
> You can use cffile to store the error files to disk.
>
> I have a system that stores a small mountain of diagnostic info via
> dumping all
You can use cffile to store the error files to disk.
I have a system that stores a small mountain of diagnostic info via
dumping all existing scopes, but that has security implications. So
instead I store the file to disk (as either a .cfm or a .html) where
it can be viewed securely. For example
You can have the error emails sent to a Gmail or Yahoo mail account,
if you don't mind the security implications of doing that.
Using an external monitoring probe could help address the issue of the
database not being accessible, and can address the problem of other
major errors that might have ev
Terrence,
You are absolutely correct! This is just a stop gap measure till the larger
problems with infrastructure, network or exchange can be addressed.
Unfortunately, the newspaper I work for is very cash strapped and slow to a
address these issues.
I have reservations about using the serve
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 exi
Instead of a database, you could use a plain text file or an xml file.
Mingo.
Scott Newsome wrote:
> Mike thanks for your reply.
>
> The database option is not workable because if the database fails (which in
> the past has been our biggest headache). We wouldn't get any emails. I could
> see chec
Mike thanks for your reply.
The database option is not workable because if the database fails (which in
the past has been our biggest headache). We wouldn't get any emails. I could
see checking for the database first, and if it's up, doing as you said. But
if it's down I still need to be able to t
You could log errors into a database table and have a scheduled task
E-mail them out in a controlled way. I find it helps to send errors to
a dedicated error E-mail account so my real accounts do not get
flooded when something bad happens.
-Mike Chabot
On 7/17/06, Scott Newsome <[EMAIL PROTECTED]
Thanks in advance for any assistance.
I am researching away to throttle the creation of email messages used to
notify system admins when ColdFusion throws an error. We have had a problem
of over-loading our exchange server when there is a database failure or some
other error that effects a lot of
9 matches
Mail list logo
