logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominik Psenner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-387) Mysterious characters in the log file
Date Tue, 13 Aug 2013 07:57:58 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737959#comment-13737959

Dominik Psenner commented on LOG4NET-387:

LOG4NET-360 is related to the EventLog appender. Since you viewed the logfile in notepad I'm
assuming you are logging into a file, which narrows down the list of possibly malicious appenders
to the FileAppender and the RollingFileAppender.

"It seems sometime I'm receiving a huge response which cause this issue?!" strenghtens my
hypothesis that your service is logging a message with binary content. Please verify if that's
the case.
> Mysterious characters in the log file
> -------------------------------------
>                 Key: LOG4NET-387
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-387
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.10
>         Environment: Windows XP, .Net 2.0 Framework, Windows Service Application
>            Reporter: Baha
>            Priority: Blocker
>              Labels: bug
>             Fix For: 1.2.10
> We have a windows service application in production. This windows service is logging
greatly with no issues, but sometimes it starts logging mysterious characters like in this
> https://files.secureserver.net/0sq7H3khXnoq67
> To fix this, we clean the log file, and restart the windows service again, but in this
way, we are loosing most of the logs (specially the exception/error fired by the windows service).
> Any idea on this will be greatly appreciated.
> Baha Ashour,
> RFID Enabled Solutions
> baha@resrfid.com 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message