This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

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 an RPD Id and a time stamp. Following the time stamp is a detailed information about the thread.

The format for the thread log file is as follows:

<THRD> <RPCId> /* <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

 rpc_idIdentifier that allows an RPC origin and RPC destination to recognize each other.

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> <0000000097> /* Wed Oct 14 2015 18:03:39.3540 */ Thread Id 326(thread number	1) on ADMIN queue started.
<THRD> <0000000097> /* Wed Oct 14 2015 18:03:39.3870 */ Thread Id 327(thread number	1) on ALERT queue started.
<THRD> <0000000097> /* Wed Oct 14 2015 18:03:39.3900 */ Thread Id 328(thread number	1) on FAST queue started.
Was this page helpful? Yes No Submitting... Thank you

Comments