As I mentioned in a private email to you, the most likely cause I can think of is
that application code is calling confgure() (using of of the Log4j Configurator
classes) at some point during the running application. If the application is
using the same Log4j Logger Repository as the server, then any call to confgiure()
will modify the server's logging configuration, which could explain the sudden
lack of logging to server.log.
Note that it is bad form for an application to call configure() unless it first
ensures it is using it's own Logger repository. Usually one would set up a
ServletContextListener that takes care of this, giving the deployer the choice of
calling configure() or not by including the configuration in web.xml or not.
I do not use JBoss, so I'm not 100% sure what the solution might be. I know they
have a special unified classloader concept so, I'm not sure how well the following
suggestion might work, but you can try it...
Try configuring any webapp that runs under JBoss to use child-first (otherwise
know as parent-last) classloading. Make sure you place log4j.jar in WEB-INF/lib.
This will insulate your server Log4j configuration from getting overwritten by
calls to configure() by hosted applications. JBoss docs describe this an other
solutions...
http://docs.jboss.org/process-guide/en/html/logging.html#d0e3286
http://community.jboss.org/wiki/log4jrepositoryselector
Someone also described the process in 3 simple steps for JBoss-4.2.2...
http://community.jboss.org/message/198690#198690
Also, for JBoss-6.0+, there is, apparently, a new POJO Logging Service that you
might want to read about.
https://community.jboss.org/wiki/LoggingPOJOServiceRequirements
Note that I obtained all this information from a quick Google search. Much more
information is out there. I encourage you do some research.
Jake
On 3/26/2010 5:59 AM, Baskaradoss, B - SPLXM wrote:
Hi,
Can you please help me for the below mentioned issue?
I'm Working as deployer and server administrator. We use Jboss 4.0x AS
to deploy our applications.
The issue I'm facing is,
Whenever we redeploy/restart the server, server.log is getting created
but after sometime the logging goes off. Yes it is not at all updating
the server.log file. Due to this, we could not trace the other critical
issues we have. Actually we have two separate nodes and we do
deploy/restarting the server separately on two nodes. We are facing the
issue in both of our test and production environment. I could not trace
out where exactly the issue is. Could you please help me in resolving
the issue?
If we have any other issues, we can check the log files. If log itself
is not getting updated/logged, how can we move further in analyzing the
issues without the recent/updated logs?
Regards,
Balaji
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
