I would say that the standard practice is probably to use your logging
subsystem to email you the exception.
For example, if you are using log4j to log, you could add something like
this to your log4j.xml file:
appender name=ERRORMAILER
Wow, that's a very nice solution. Thanks :))
-- Edvin
Sebastiaan van Erk skrev:
I would say that the standard practice is probably to use your logging
subsystem to email you the exception.
For example, if you are using log4j to log, you could add something like
this to your log4j.xml file:
It is a really good way to blow up your exchange server... We had a
bug somewhere that generated exceptions in an endless loop. It took
exchange over a whole day to empty the queue.
Martijn
On 3/10/08, Edvin Syse [EMAIL PROTECTED] wrote:
Wow, that's a very nice solution. Thanks :))
-- Edvin
Logging stuff in endless loops is generally a good way to blow things
up. ;-) I remember back in my university days a friend of mine did some
logging on /tmp on 150 or so Sun workstations. It went into an endless
loop and all of the workstations became inaccessible (/tmp and virtual
memory
