Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of elecharny@gmail.com designates
 209.85.132.241 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=lDqSzrtcP8YrmeyrxDEgrHd5vHEA/aAtLyG/pX80NX4huo6Jh6LGZ7HOvgS93ESyQPHNYeL3M5mGmOZWulv86H/XcYCxzgDqShuufBeuhdRxJr6YsfZ4eUpWXIZ0j7L9dCboePBJDAc9/Repg7Y8C+jrXIS9hSrbcYCo6faOaAw=
Message-ID: <d45b08f00706290020t5f8b6ecep20d9150e22c112ed@mail.gmail.com>
Date: Fri, 29 Jun 2007 09:20:48 +0200
From: "Emmanuel Lecharny" <elecharny@gmail.com>
Reply-To: elecharny@iktek.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: nlog4j problems under load
Cc: user@slf4j.org, ceki@qos.ch
In-Reply-To: <f275eef10706281914i64c7b629k6bc2b9425c6bfa3e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <f275eef10706281914i64c7b629k6bc2b9425c6bfa3e@mail.gmail.com>

Hi Norval,

good to see that you are back !

I hope Ceki can help you on this, because I'm afraid we are not
exactly Log4j specialists on Directory project... What about Logback,
does it behave the same ?

Emmanuel

On 6/29/07, Norval Hope <nrhope@gmail.com> wrote:
> Hi,
>
> I am in the final stages of preparing a release that builds on top of
> ApacheDS, and consequently must use an slf4j compliant logging library so=
 I
> used nlog4j 1.2.25 (as AD does).
>
> I have a requirement to have separate appenders created dynamically at
> runtime and adopted the approach shown in the small attached test/config
> files, which was:
>   1. to have a template appender copied every time a new appender is
> required
>   2. have a stub logger used only so that I can discover the template
> appender when I need it (as the template appender is in this loggers
> appender list in the .properties config file)
>   3. to dynamically create a logger intended to send output to the
> dynamically created appender only (additivity is false and no other logge=
r
> knows about each particular appender instance).
>
> This all works fine under normal load, but noted some problems under heav=
y
> logging load so I wrote the stand alone test to investigate.
>
> Running the test with 2 threads and no delay ("java nlog4jtest.NLog4jTest=
 2
> 0") causing problems immediately on a dual core laptop running windows xp=
:
>   1. log messages from one logger appear against appenders to which they =
are
> not linked
>   2. partial log messages are evident, where headers are missing etc.
> Using a delay of 5 milliseconds improved the situation but still both
> problems were evident.
>
> On a single cpu windows box running xp, "java nlog4jtest.NLog4jTest 10 0"
> also evidenced both problems too.
>
> I know I'm making use of a bespoke approach here, so I'm hoping I'm doing
> something wrong in my implementation or breaking some contract I'm not aw=
are
> of. I basically can't ship with logging in this state and can't migrate t=
o
> logback due to LGPL license, which is a problem for the ApacheDS project
> too.
>
> Any expert advice about alternative implementation approaches or how to b=
est
> approach debugging would be greatly appreciated.
>
> Many Thanks,
> Norval
>


--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com