Hi, When an appender's doAppend method throws an exception, it unwinds through the call stack. At the very least, this means that the log message won't be passed to any other appenders that might otherwise process it. It seems to me that log4cxx needs to protect calls to doAppend with a try/catch(...) block that squelches the errant exception.
In my case, the exception escaped all the way up to a ->log() call
from one of my destructors, which caused bad things to happen...
--jtc
--
J.T. Conklin
