logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Johan Sandgren <...@svep.se>
Subject SV: Dual logging problem - outofmemoryerror... heap space
Date Wed, 08 Oct 2008 14:55:48 GMT
Thanks for your suggestions Bruno

I'll give you more info.
The system will be running for a long time, and people won't be there to read the logs searching
for errors being logged, before the logfiles are rotated and overwritten again.

That's why I need to extract the errors to another file, with some history too, for making
it clear to the programmer (me), what happened, why the error occurred :)

And about the finegrained details... I need them always on, to get detailed error-info-history.
It's kind of eating the cake (get full debug log), and only when I need it (keeping the cake,
not eating). Ha ha

I think I traced a memoryleak now, using the superb tool "yourkit". If you haven't tried it,
I recommend it. They offer free trial license, 7 days working or so.


-----Ursprungligt meddelande-----
Från: Bruno Melloni [mailto:Bruno.Melloni@wnco.com]
Skickat: den 8 oktober 2008 16:37
Till: Log4J Users List
Ämne: RE: Dual logging problem - outofmemoryerror... heap space

This might be a dumb question/answer... but instead of using the spy
class, why not stick to the RollingFileAppender and simply increase the
max file size or the number of backup files kept, so that you keep
enough logs?

Or, if you don't have the disk space, why not use the finer grain
control - by package or class - in log4j.properties so that you only
send to the logs the 'critical information' instead of everything?  That
way your logs will be smaller.

BTW, you may even have an unrelated memory leak that is reducing the
memory available to log4j.



From: Johan Sandgren [mailto:jsa@svep.se]
Sent: Wednesday, October 08, 2008 3:20 AM
To: log4j-user@logging.apache.org
Subject: Dual logging problem - outofmemoryerror... heap space


Need advice from professionals here... I'm stuck! L

I'm using log4j, and my logs are rotating quite fast, so if an error
occurs, for example in the middle of the night, it will not be present
in the log in the morning when I arrive to check for errors.

So I decided to extract the errors live, when they occur, and make them
go to another file.

But since errors just on their own does not say much of where the
program were and what was the variables right then, I'd also like to
attach some history before the error in the error.log-file.

So I wrote a class to support this feature. It's a spy really. It's
attaching to an existing logger, and adding another appender, which I
use to create history and outputting to another error.log-file when I
need to.

A little more details on the spyclass are:

I'm calling my usual logger X, and I've created another loggerclass Y,
which attaches another appender on my X.

For each logger call with X, I also call my Y which is getting the
string too, because it's snooping on X, via this appender I added. Y is
also keeping a circularbuffer of history of all logging it gets.

When Y is called with error, fatal or warn, it will do a dump of the
history and lastly, the erranous line, and all this to another file,

That way I will get my usual log in blabla.log, and for each warn, error
/fatal, I get a few lines of history + the error/warn/fatal-line that is
to be noticed.

My problem:

BUT, I get out of heapmemory when using it after a while.

I cannot find the error causing it. Mayber I'm misusing the appender or

I've attached the historymaking class "ErrorLogger.java", and an example
(test.java) of how the calls are made.

Exception in thread "Thread-5" java.lang.OutOfMemoryError: Java heap



        at java.lang.StringBuffer.append(StringBuffer.java:225)

        at java.io.StringWriter.write(StringWriter.java:79)






        at org.apache.log4j.Category.callAppenders(Category.java:203)

        at org.apache.log4j.Category.forcedLog(Category.java:388)

        at org.apache.log4j.Category.debug(Category.java:257)

com.sttcare.alarmSwitch.JmsTester.activeMqIsUp(JmsTester.java:88) calls
connection.stop(); So it really has nothing with log4j, I guess the heap
is just ended right then.



        at java.lang.Thread.run(Thread.java:595)

Seems to me something is exandCapacity too much...



Johan Sandgren

Svep Design Center AB

Phone +46 46 192 722

Mobile +46 70 173 4152

Box 1233, 221 05 Lund, Sweden

E-mail   jsa@svep.se

Website www.svep.se <http://www.svep.se/>

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

View raw message