[SERVER-6555] Stack traces should show thread name Created: 22/Jul/12  Updated: 11/Jun/15  Resolved: 11/Jun/15

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Tad Marshall Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18605 Include thread id in log messages Closed
Participants:

 Description   

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.



 Comments   
Comment by Andy Schwerin [ 11/Jun/15 ]

This was fixed sometime in the past when I rewrote the logging subsystem.

Comment by Tad Marshall [ 22/Jul/12 ]

Retitled ticket to specify goal instead of method.

Comment by Eliot Horowitz (Inactive) [ 22/Jul/12 ]

We can't do this as stated as log() uses too much of the system.
Need to be a bit lower level.

Generated at Thu Feb 08 03:12:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.