Server Reference Guide : D. OpenROAD Server Pooler Event Log : SPO Log Description : Example 9: Stopping a Slave
 
Share this page                  
Example 9: Stopping a Slave
A slave is stopped by terminating the ASO process that is associated with it. Slaves can be stopped for a variety of reasons, but the most common are timeouts and shutdown. Slaves can also be stopped because of fatal Initiate errors or fatal Call4GL errors returned by an ASO. (Because certain classes of errors may leave the ASO in an unstable state, the ASO process must be sure to be restarted before allowing any further calls.) Slaves will also be stopped when the configured ASO transaction limit has been reached. The log record for a slave stop event will include the reason in parentheses.
The log record for a slave stop event also includes a dump of the current slave statistics in the same format as a slave snapshot event. The following example shows a slave that was stopped because of a timeout.
2007/09/06_16:05:44.871   STOPPING: S3 (due to timeout)
                                         cnt        min        max        avg
                    QueueUse/Depth:      602          0          1          0
                         QueueWait:                   0ms        0ms        0ms
                         Initiates:        1        453ms      453ms      453ms
                          Call4GLs:      600          0ms      125ms       10ms
                       ASOTrxCount:      600