Hei Thorsten Schöning, 2012/9/14 Thorsten Schöning <[email protected]> > am Freitag, 14. September 2012 um 17:33 schrieben Sie: > > > I won't do > > more about it as we will most likely move away from log4cxx soon. > > What's the alternative you decided for and why? I need to consider a > move as well in the future.
We have experimented with log4cxx in COM objects which are called from a PHP web site. Our conclusion from that experiment is that log4cxx is designed to be initialized once during process startup, which we can't easily do. The bug in APRInitializer is one thing, but there are other clues as well, e.g. singleton instantiations that aren't thread safe. The COM objects have proprietary logging functions we tried to get rid of, so for now we'll just switch back to those. I'd like to add that log4cxx has served us well for years in some high-availability systems where the last thing you want is a service degradation due to a faulty logging library. Currently, we have no plans to replace log4cxx there. Kind Regards Bjørn Thirud
