[
https://issues.apache.org/jira/browse/LOG4NET-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737952#comment-13737952
]
Baha commented on LOG4NET-387:
------------------------------
Thanks for your quick response!
Well, I just found this link:
https://issues.apache.org/jira/browse/LOG4NET-360
It seems it's something related to the string length log4net is writing to the
file, could it be the case?
All what I'm doing is logging the response coming from a webservice. It seems
sometime I'm receiving a huge response which cause this issue?!
I will try to reproduce and send you the app.
Thanks again for you quick response!
> 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 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 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
