Hot deploy is when you load a new version of a war for example while the
server is still running. This triggers a chain of init actions on the server
side.
I see from the logs the doGet method in the servlet caused a init of log4j
configuration.
try looking in that direction. I think this should
No, there was no any hot deployment. We deploy our application WAR file and
restart tomcat. This is a must for us. And there was no any change to Log4J
library jar file.
BR,
Shahnaz Ali.
On Thu, Apr 8, 2010 at 12:13 PM, Yair Ogen yairo...@gmail.com wrote:
Hot deploy is when you load a new
Hopefully more explanation can attract some ideas here.
I am using XML configuration and a custom appender. So I have one section in
the XML corresponding to one logger name and one log file.
So for each different logger name, log file and the same custom appender I
need to add one more section
On 8 April 2010 07:47, Shahnaz Ali shaan20...@gmail.com wrote:
No, there was no any hot deployment.
But the evidence points to a change of class so something equivalent
to a redeployment must have happened. Something caused a deployed
class to be reloaded and that operation failed due to a class
Hi,
Its not possible to do these kind of experiments in running production
server. But i am sure there is nothing happened like redeploying new war,
jar or any kind of change. Server was untouched for last several hours.
Logs are not fabricated, yeah i took only the portion when problem started.
On 8 April 2010 10:27, Shahnaz Ali shaan20...@gmail.com wrote:
Its not possible to do these kind of experiments in running production
server. But i am sure there is nothing happened like redeploying new war,
jar or any kind of change. Server was untouched for last several hours.
Don't you have
If I understand you correctly, you want to have several loggers all using the
same appender?
Use the hierarchical approach of the logger repository by prefixing your logger
names:
logger name=loggerFamily1.Test1
level value=info/
/logger
logger
