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
I have been unable to reproduce the problem on Ubuntu Linux 6.06-1
and gcc 4.0.3 running under VMWare Fusion on Mac OS/X either in
single processor or double processor mode. That is the glorious
thing about race conditions, the slightly little change might hide
them. Thanks for the output
On Jun 29, 2007, at 11:37 PM, [EMAIL PROTECTED] wrote:
If you just build the small program that I sent and link it to the
subversion log4cxx, then check out the log files it creates.
They're full of junk along with valid lines too.
It does it everytime. I'm working on a threaded project
If you just build the small program that I sent and link it to the subversion
log4cxx, then check out the log files it creates. They're full of junk along
with valid lines too.
It does it everytime. I'm working on a threaded project that uses 100's
of threads, and it was always working great w
On Jun 29, 2007, at 10:53 PM, [EMAIL PROTECTED] wrote:
Nevermind. This is a known bug.
http://issues.apache.org/jira/browse/LOGCXX-129
I should of just stayed with 97 which was working fine.
Thanks,
Pete
LOGCXX-129 only reported problems with AsyncAppender which was badly
flawed in l
Nevermind. This is a known bug.
http://issues.apache.org/jira/browse/LOGCXX-129
I should of just stayed with 97 which was working fine.
Thanks,
Pete
On Fri, Jun 29, 2007 at 06:09:26AM -0700, [EMAIL PROTECTED] wrote:
>
> Hi, I've been using the subversion log4cxx-10.0.0, which is currently
