Thanks Brown for the reply.
The following was the reply given by Bender Heri
Your problem is a classloader issue. Keep in mind that the Logger-Universe
which you initialize within your static method is globally the same within
the same classloader. Annother classloader would initialize another
logger-universe. You have to elaborate which class is loaded by which
classloader. This depends on the application server you use, its
configuration and your deployment.
Search the archives for "MultiFileAppender" and "RepositorySelector". There
are plenty of ideas how to separate log files depending on the context.
The jboss app server gives an option like
<!-- A flag indicating if ear deployments should have their own scoped
class loader to isolate their classes from other deployments.
-->
<attribute name="Isolated">true</attribute>
which we have set as true. Thus different applications have different class
loaders and from the reply of Bender i could understand that there are
different logger-universe defined. Consider that The LogManager which i
have mentioned earlier is in a jar file. This jar file is shared across all
the EAR files. The log4j.properties file alone differs for each module. I
could not figure out on how to use the RepositorySelector when my LogManager
does not extend the log4j's LogManager . Any thoughts?
--
View this message in context:
http://www.nabble.com/Logging-done-in-the-wrong-files-tp25411329p25471153.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
