On 01/04/2010 12:41 PM, WM YEOH wrote:
Hi Ceki,
Thank you for the guidance.
I think I better start all over again what was the actual problem to give
you a better picture.
I am currently upgrading the sun one apps server from 7.1 to 9.1 (in UNIX
platform), common-logging.jar, jakarta-log4j-1.2.6.jar and log4j-1.2.15.jar
are currently specified in the server classpath. The logging problem
occurred after upgraded to 9.1.
You should not have both jakarta-log4j-1.2.6.jar and log4j-1.2.15.jar on the
server's class path. Pick one and only one.
I have an EAR file containing few jars (EJB involved) and a war file
deploying in a standalone instance. I have another war file deployed within
the same instance, meaning there are 2 apps running in one instance. When
the instance startup, there are suppose to have 2 log files, for instance
A.log and B.log. However, all the loggers only written in a single log, take
A.log as an example. Both apps have their own initServlet to load the log4j
configuration files.
I need some answers from you in order to clear my doubts,
- is logback my only solution?
No, logback is not your only solution. You could change the problem
setting by using non-static logger references in your EJB
classes. With the simplified problem you could stick with
log4j. Having said that logback is the only platform that deals with
the logging separation problem for shared classes with static loggers.
Given that the rest of your post is logback related, I posted my full
answer on the logback-user mailing list [1]. If you wish to pursue the
logback-based solution, then please continue the discussion there.
[1] http://www.qos.ch/pipermail/logback-user/2010-April/001524.html
--
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
