-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Logging
-
None
It is not always clear which thread is printing a stack trace, and some conditions can cause more than one thread to print a stack trace. It would be easier to interpret stack traces if they were logged as other messages are, by using log() instead of cout.
- related to
-
SERVER-18605 Include thread id in log messages
- Closed