RE: Logging stops after hours working - Mistery solved

[Cristian Jansenson <cj...@brownstone.net>]

Mistery solved... we are using an old version of a e-spreadsheet software
that had a log4j-related bug. Their software basically turned off logging,
and it is documented here:

http://esupport.actuate.com/es/download/actuate7sp1updatedocs/readme.pdf



Thanks for your help,



Cristian Jansenson

-----Original Message-----
From: Cristian Jansenson [mailto:cjansenson@brownstone.net] 
Sent: Thursday, January 18, 2007 4:31 PM
To: 'Log4J Users List'
Subject: RE: Logging stops after hours working

Thanks Jake.  I suspect there is a threading problem in the app that is
causing this issue.  Your clarification that is not a problem already
encountered in log4j package helps a lot.  Thanks,

Cristian Jansenson


-----Original Message-----
From: Jacob Kjome [mailto:hoju@visi.com] 
Sent: Tuesday, January 16, 2007 10:58 PM
To: Log4J Users List
Subject: RE: Logging stops after hours working


The behavior is curious.  I would guess that some other library is 
configuring Log4j on it's own.  This doesn't have to be via a config 
file.  It could be just doing it programmatically.  I take it you 
searched for both log4j.properties *and* log4j.xml.  You only 
mentioned the former, so I thought I'd make sure.  This one's a tough 
nut to crack.  I'm not sure I can say anything other than good luck 
finding the source of the problem!

BTW, the printing you see is being printed by LogLog, which is Log4j 
bootstrap logger.  Log4j 1.3 uses standard Log4j logging to log its 
own messages.  Log4j 1.2.xx uses LogLog to log its own messages.


Jake

At 07:59 PM 1/16/2007, you wrote:
 >More to add to this case:
 >
 >- We are not using any special classloader, and there is no other
 >log4j.properties hanging around that the IDE or grep could find.
 >- We didn't extend the log4j code by writing Appenders or other classes.
 >- We are only using the basic Logger methods (.error() .warn(),
 >.isDebugEnabled(), etc)
 >- This is a multithreaded application running a home-made web-server.
 >
 >Clarification on the lines logged:
 >
 >... Some unrelated logging here that is not log4j-related here... the last
 >log4j-related loged info is hours before.
 >log4j: Hierarchy threshold set to [OFF].
 >log4j: Could not find root logger information. Is this OK?
 >log4j: Finished configuring.
 >... no more logging here
 >
 >Thanks,
 >
 >Cristian Jansenson
 >
 >-----Original Message-----
 >From: Cristian Jansenson [mailto:cjansenson@brownstone.net]
 >Sent: Monday, January 15, 2007 10:12 AM
 >To: log4j-user@logging.apache.org
 >Subject: Logging stops after hours working
 >
 >I am running an application that uses log4j version 1.2.9.  The
application
 >is running on Java 1.5.0.9 for Linux 64-bit version.  After minutes or
hours
 >of running and logging, log4j stops logging.  The console shows the
 >following message, which partially explains the reason:
 >
 >
 >
 >log4j: Hierarchy threshold set to [OFF].
 >
 >log4j: Could not find root logger information. Is this OK?
 >
 >log4j: Finished configuring.
 >
 >
 >
 >But why does this happen?  Since this information is printed from the
 >PropertyConfigurator, It looks as if log4j were re-configuring, even
though
 >I am NOT using the configureAndWatch method, and the log4j.properties file
 >was neither touched nor changed.
 >
 >
 >
 >My log4j.properties:
 >
 >
 >
 ># enable log4j debugging, and set threshold=ALL (see bug 10598)
 >
 >log4j.threshold=ALL
 >
 >log4j.debug=true
 >
 >
 >
 ># Set root logger level to DEBUG and its only appender to A1.
 >
 >log4j.rootLogger=ERROR, A1
 >
 >log4j.logger.http=WARN, HTTP
 >
 >
 >
 ># see bug 10603:  http should not inherit appenders, etc, from root.
 >
 >log4j.additivity.http=false
 >
 >
 >
 >log4j.appender.A1=org.apache.log4j.DailyRollingFileAppender
 >
 >log4j.appender.A1.File=logs/error-${port}.log
 >
 >log4j.appender.A1.DatePattern='.'yyyy-MM-dd
 >
 >
 >
 ># A1 uses PatternLayout.
 >
 >log4j.appender.A1.layout=org.apache.log4j.PatternLayout
 >
 >log4j.appender.A1.layout.ConversionPattern=%d{DATE} %x [%t] %-5p %c %x -
 >%m%n
 >
 >
 >
 >############################################
 >
 ># HTTP Log config
 >
 >############################################
 >
 >
 >
 >log4j.appender.HTTP=org.apache.log4j.DailyRollingFileAppender
 >
 >log4j.appender.HTTP.File=logs/http-${port}.log
 >
 >log4j.appender.HTTP.DatePattern='.'yyyy-MM-dd
 >
 >
 >
 ># A1 uses PatternLayout.
 >
 >log4j.appender.HTTP.layout=org.apache.log4j.PatternLayout
 >
 >
 >
 >log4j.appender.HTTP.layout.ConversionPattern=%m%n
 >
 >
 >
 >
 >
 >I hope you can help me on this issue,
 >
 >
 >
 >Cristian Jansenson



---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.16.13/632 - Release Date: 1/16/2007
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.16.14/636 - Release Date: 1/18/2007
 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.16.14/636 - Release Date: 1/18/2007
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.4/643 - Release Date: 1/21/2007
 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org