[logback-dev] logback is overwriting the log file in the wrong appender

[Stefanus Arvin]

Hi There,

Just want to iterate what I've mention in Jira: LOGBACK-847<http://jira.qos.ch/browse/LOGBACK-847>

I found an issue when I'm running it under the load:

I'm running the logback under the log using the log4j adapter.
in the log4j.xml, I setup the logging with async appender which would write to fileRolling appender that would roll every hour.

During the load, I found that I missed 1 hour worth of logging.
When I look at the file, the new coming log file were actually overwritten the previously written log.

Example:



Filename


On the load


Normal behaviour


server.log2013-04-23-16


Wring the file at 23/4/2013 from 17.00-17:59

I could not find the log at 23/4/2013 from 16.00-16:59


Wring the file at 23/4/2013 from 16.00-16:59


server.log2013-04-23-17


Wring the file at 23/4/2013 from 18.00-18:59


Wring the file at 23/4/2013 from 17.00-17:59



I'm using the following stack to run logback:
§  jcl-over-slf4j-1.7.5
§  log4j-over-slf4j-1.7.5
§  jul-to-slf4j-1.7.5
§  logback-classic-1.0.11
§  logback-core-1.0.11

Note that it's behaving normal if it's not under the load.

I'm not sure if this is a bug in logback async or in the log4j adapter.

Appreciate if someone can help me investigate this issue.



Thanks,

Arvin.


EMAIL DISCLAIMER This email message and its attachments are confidential and may also contain copyright or privileged material. If you are not the intended recipient, you may not forward the email or disclose or use the information contained in it. If you have received this email message in error, please advise the sender immediately by replying to this email and delete the message and any associated attachments. Any views, opinions, conclusions, advice or statements expressed in this email message are those of the individual sender and should not be relied upon as the considered view, opinion, conclusions, advice or statement of this company except where the sender expressly, and with authority, states them to be the considered view, opinion, conclusions, advice or statement of this company. Every care is taken but we recommend that you scan any attachments for viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-dev/attachments/20130426/2cdfa62c/attachment-0001.html>