Thread log
The thread log traces the history of when threads start, as well as how many times a thread has failed and been restarted by Thread Manager. By default, the log file is named arthread.log.
Each transaction begins with the <THRD> prefix, followed by a time stamp. Following the time stamp is detailed information about the started thread.
The format for the thread log file is as follows:
<THRD> <trace ID> /* <ddd mmm dd yyyy hh:mm:ss:nnnn> */ Thread Id <threadID> (thread number <threadNumber>) on <queueType> <tStatus>.
The following table explains the possible values for the entries in a thread log file.
Possible values for thread log file entries
Entry | Possible value |
---|---|
trace_id | A common identifier that helps to trace the flow of execution of APIs across log files. |
thread_id | Identifier of the server running thread (fixed-size, 10-digit number). |
thread_number | A sequential number assigned to the thread. This number helps recognize the thread from Windows Performance Monitor. |
queue_type | The queue this thread lives on (for example, admin, alert, fast, list, escalation, or private). |
t_status | A value of "started," "died," or "restarted". |
The following are sample thread log entries:
<THRD> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> <0000000031> /* Thu Jan 05 2017 01:42:29.7800*/ Group/User Change Received: tid=31 lastGroupChangeTime=Thu Jan 05 01:25:09 EST 2017, Add request to Admin Queue
<THRD> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> <0000000662> /* Thu Jan 05 2017 01:42:34.8120 */ GroupChangeRecache: tid=662 delayRecacheTime=lastGroupChangeTime=Thu Jan 05 01:25:09 EST 2017, Add request to Admin thread
<THRD> <TrID: jluKP-XvREC67KMqouHuvQ:0000026> <0000000023> /* Thu Jan 05 2017 01:42:56.3070 */ Group/User Change Received: tid=23 lastGroupChangeTime=Thu Jan 05 01:42:34 EST 2017, Add request to Admin Queue
Comments
Log in or register to comment.