Bug #278
WLogger isn't thread safe
| Status: | Feedback | Start: | 01/22/2010 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assigned to: | Wim Dumon | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
When logging from another thread it mixes the buffer with other logs.
This makes it very hard to debug or just show logs.
History
Updated by Wim Dumon 7 months ago
- Priority changed from Immediate to Low
- Status changed from New to Feedback
To avoid this:
1. start your wt application with --num-threads=1. This is usually acceptable during debugging.
2. reroute access logs to a file with --access-log=somefile.log
3. reroute the application log to a file (see wtconfig.xml)
we could do something about access log messages running into each other, if required. This is however not trivial in all cases (multi-process deployments). I propose to implement this when this turns out to be problematic.