I've created bug LOGCXX-186 (https://issues.apache.org/jira/browse/
LOGCXX-186) for this issue including much of the recent thread on
log4cxx-user. Further discussion and work should occur either within
the bug report or on log4cxx-dev.
On Sun, Jul 01, 2007 at 03:49:44AM -0700, [EMAIL PROTECTED] wrote:
> Hmm., that's really odd. I can reproduce it on my two boxes with pent4
> with hyperthreading enabled, but I can't on my weenie single lapetop cpu.
I forgot to mention, that if I disable hyperthreading in the bios, then
the probl
Hmm., that's really odd. I can reproduce it on my two boxes with pent4
with hyperthreading enabled, but I can't on my weenie single lapetop cpu.
I'll try this and get back to you.
LOG4CXX_LOCALE_ENCODING_UTF8=1
Thanks,
Pete
On Sun, Jul 01, 2007 at 01:34:22AM -0500, Curt Arnold wrote:
> I have
On Saturday, June 30, 2007 7:27 AM, Curt Arnold wrote:
>
> LOGCXX-129 only reported problems with AsyncAppender which
> was badly flawed in log4j 1.2.13 and earlier and deadlock
> reports in log4j started getting more frequent. The log4cxx
> AsyncAppender was pretty much a straight port of the
