I have looked at the source here and I have a question.
Since the log4j extras has other methods of rolling over that are time based
I thought if we schedule the rename for a lean period when there is not much
log file updates then there would be no problem. Am I on the right track ?
What about
Hi,
I try to use DOMConfigurator.subst to change dynamically in Java code
location of the output logging file. See log4j.xml below.
The following code is called in main method to set up file location:
private static void setLogging(final String logDirectory, final String
logFileName) {
Thanks.
The log files are also different for each logger but the log file
configuration is inside the appender configuration !
--
View this message in context:
http://old.nabble.com/Multiple-log-files%2C-multiple-logger-names-and-the-same-appender-tp28024737p28179638.html
Sent from the Log
We have test server but how we will create actual load on that. Recreating
this problem is a challenge. After restarting, its working fine from last
around 3 weeks. One server receives 80,000 call requests in a day on
average. Since then no issue It is basically serving VXML for telephony
calls
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:
On 8 April 2010 10:27, Shahnaz Ali 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 an identical test
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 07:47, Shahnaz Ali 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
incompatibility. Th
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
