logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From benedikt herudek <benedikt.heru...@gmail.com>
Subject Re: concurrency issues with one log file for multiple
Date Sun, 21 Jun 2009 07:31:47 GMT
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
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message