
| Key: |
LOG4NET-84
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Invalid
|
| Priority: |
Minor
|
| Assignee: |
Nicko Cadell
|
| Reporter: |
Tal G
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
28/Jul/06 10:36 PM
|
|
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.
|
|
Description
|
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.
|
Show » |
made changes - 28/Jul/06 10:36 PM
| Field |
Original Value |
New Value |
|
Assignee
|
|
Nicko Cadell
[ nicko
]
|
|
Status
|
Open
[ 1
]
|
Closed
[ 6
]
|
|
Resolution
|
|
Invalid
[ 6
]
|
|