tnx guys, problem solved.
we've built an intranet application according to j2ee
architecure. log4j was configured in init-servlet and
that happens after ejb's are loaded (i guess...)
anyway, Loggers were initialised before log4j was
initialised properly.
solution: we're using a custom made
Howdy,
Are you sure you don't have a console appender defined as well? Are you
sure log4j is configured well, i.e. without errors? Are you running
within a container that's also using log4j?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Ruud Steeghs [mailto:[EMAIL
Log4j, by default, uses a single logger repository. So, unless you log
within the context of your own custom logger repository, the last entity to
configure log4j will have configured log4j for every app using the default
logger repository. This is not usually a concern in a standalone app,
