[ http://issues.apache.org/jira/browse/LOG4NET-84?page=comments#action_12423990 ] Ron Grabowski commented on LOG4NET-84: --------------------------------------
You solved your problem...do you still think this is an issue for log4net in general? I don't understand how log4net is suppose to synchronize messages so they get written in the correct time order. What if I'm trying to test out a new threading algorithm and I want messages to be written in the order in which they were processed by the application or something I don't have control over (i.e. the operating system)? > Allow messages to be printed in ascendant order according to date time. > ----------------------------------------------------------------------- > > Key: LOG4NET-84 > URL: http://issues.apache.org/jira/browse/LOG4NET-84 > Project: Log4net > Issue Type: Improvement > Components: Appenders > Affects Versions: 1.2.10 > Environment: All > Reporter: Tal G > Priority: Minor > > In multi threading application, when letting log4net to print time > information before every message (for example with %d{HH:mm:ss.fff} layout), > it might print the messages not according to ascendant order. > The reason is that the date time information is taken from > LoggingEventData.TimeStamp field that is update to Now before the > synchronization phase. > That is only semantic issue, but it cause inconveniency to many. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
