Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of benedikt.herudek@gmail.com
 designates 209.85.220.211 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=BTVkSxttQQJELW6MemZEF6O4Gt+jeMel+USbk39TKspAj6z5MzyV3ZM7bPtP60AQ70
         t3dAUy6Z1YGdoPYh/uOCV6mEiYZ19r72mN85b+cud5GyN7/gaeqA1DOIUJ9EkuNlebL2
         +UES83X5kBAnci6VBgtx1duBsEJEuRJwqqJgM=
MIME-Version: 1.0
In-Reply-To: <a44e15a30906202336t6d2ed551p7cff569e683e8c6d@mail.gmail.com>
References: <a03989f50906200212k473f7f74hd385cd3a58be8cad@mail.gmail.com>
	 <a44e15a30906202336t6d2ed551p7cff569e683e8c6d@mail.gmail.com>
Date: Sun, 21 Jun 2009 09:31:47 +0200
Message-ID: <a03989f50906210031y6052b0b0p4fe4139d7ec66323@mail.gmail.com>
Subject: Re: concurrency issues with one log file for multiple
From: benedikt herudek <benedikt.herudek@gmail.com>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=0015174c358c114766046cd6c07b

--0015174c358c114766046cd6c07b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I am using one logger per session and use the name of the logger to place in
the log file, no nested diagnostic context.

threadsafe in this context means: no blocking of whole file for one session,
no building of queues I assume ... ? ... :-)

regards

Benedikt


On Sun, Jun 21, 2009 at 8:36 AM, Yair Ogen <yairogen@gmail.com> wrote:

> log4j  is thread safe and should handle the concurrency efficiently.
> I suggest you place tour OrderId in the log message using MDC.
>
> On Sat, Jun 20, 2009 at 12:12 PM, benedikt herudek <
> benedikt.herudek@gmail.com> wrote:
>
> > Hi,
> >
> > we are intending to use log4J in a call center: we have around 100
> > simultaneous sessions working on one tool to create orders. W set up one
> > logger per session (identified by basically the order id). All these
> > loggers
> > will write to one log file produced by log4J.
> >
> > Since we didnt use log4J before we want to be sure we are not creating
> > concurrency issues and performance bottlenecks with having 100 session
> > writing to one file. E.g. worst case scenario: 1st session loggs the file
> > throughout its complete session and only releases it at the end, then in
> > the
> > meanwhile all other sessions queue up and wait. Rather, we suspect, log4J
> > is
> > automatically able to handle such a multiple sessions writing to one file
> > situation and we dont have to bother with the details of that mechanism.
> >
> > Does anyone have experience, information, weblinks to documentation, tips
> > or
> > comments as to that problem ... ? ...:-)
> >
> > thx a lot !!!
> >
> > gruesse / regards / groetjes / adios
> >
> > Benedikt Herudek
> >
>

--0015174c358c114766046cd6c07b--