[
https://issues.apache.org/jira/browse/LOG4NET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig updated LOG4NET-387:
-----------------------------------
Priority: Critical (was: Blocker)
Fix Version/s: (was: 1.2.10)
I'm sure this issue is important to yoi, but so far you are the only one that
has ever reported it which makes it likely to be an environment or application
issue - that's why I've reduced the severity.
Is there anything we can do to reproduce this?
It really looks as if something was spitting a binary into your logfile, maybe
you are logging some user input? Does the last log message before the trouble
starts to happen give any hint?
> 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: Critical
> Labels: bug
>
> 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 screenshot:
> 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
> b...@resrfid.com
--
This message was sent by Atlassian JIRA
(v6.1#6144)
