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.