DESTROYING: Dispatcher
This entry is logged when a dispatcher is being shut down. This event indicates that all resources associated with an application signature have been released. When the dispatcher is destroyed, a snapshot of its state is written to the SPO log.
This event appears in the log with the following format:
Timestamp DESTROYING: DDid
cnt min max avg
QueueUse/Depth: DUseCount 0 DDepthMax DDepthAvg
QueueWait: 0ms DWaitMax DWaitAvg
CurSlaves: DCurrSlaves
ClientRefs: DClientRefs
Timestamp
Identifies the event timestamp. It has the following format:
yyyy/mo/dd_hh:mi:ss.fff
yyyy
Identifies a four-digit year value
mo
Identifies a two-digit month value
dd
Identifies a two-digit day value
hh
Identifies a two-digit military hour value
mi
Identifies a two-digit minute value
ss
Identifies a two-digit second value
fff
Identifies a three-digit millisecond value
Did
Identifies the dispatcher ID. This value is assigned when a dispatcher is created. It uniquely identifies a dispatcher instance. This identifier is not reused during the lifetime of the SPO.
DUseCount
Indicates the number of times the dispatcher has been entered to dispatch work. This value roughly corresponds to the total number of Call4GL plus Initiate requests.
DDepthMax
Indicates the maximum number of clients waiting for a slave that has been queued to this dispatcher
DDepthAvg
Indicates the average number of clients waiting for a slave that has been queued to this dispatcher
DWaitMax
Indicates the maximum time (in mSec) that a client was queued to the dispatcher while waiting for a slave
DWaitAvg
Indicates the average time (in mSec) that a client was queued to the dispatcher while waiting for a slave
DCurrSlaves
Indicates the number slaves that can be controlled by this dispatcher
DClientRefs
Indicates the current number of clients who have been assigned to this dispatcher as a result of a successful Initiate request
Last modified date: 12/20/2023