DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14997>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14997

High Throughput, High Threads, Log File not Rollingover

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From [EMAIL PROTECTED]  2002-12-04 01:29 
-------
For the past day I've been working on a test-case, but to no avail.  I haven't 
been able to reproduce it in a smaller test-case.  I did, however, just realize 
a major mistake I made which i think lead me to believe it was a threading 
problem.

Becuase my program has 2 entry points, I initialize the log4j in each of these 
separate locations.  If you look at my config I have 
log4j.appender.A1.Append=false, which means if I intialize the 2nd log4j 
instance while the 1st is logging, all of the log information the 1st had done 
will be truncated.  very bad...  I've fixed this problem and I haven't seen a 
failure to roll yet.  I'm going to continue to monitor my logging to see if the 
rolling error occurs, but i think it was just me trying to figure out what was 
going wrong.  sorry for logging an inaccurate bug, I went ahead and closed this 
bug, if I do find my log isn't rolling in the future (don't think i will) i can 
always reopen this one.

I would like to thank you for your extremely rapid response time after 
initially logging my bug, I was quite impressed.

thanks again,
scott

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to