When set to "no" disables the end-of-task mutex sweep.
Restriction: This topic applies only when the Enterprise Server feature is enabled.
Syntax:
mutex sweep enabled=yes-or-no
Properties:
Default:
yes
Comments:
From Enterprise Server 7.0 Patch Update 2, performance of the mutex-sweep process has been improved.
Micro Focus recommends that you do not use this setting to disable the mutex sweep.
[2]
This sweep is a defensive measure that is typically performed at the end of each task. It checks to verify that the task does
not end with any mutexes locked. A locked mutex at that point can only be the result of a logic error. The sweep ensures that
such an error does not block the processing of any new requests.
Typically, it is not recommended to change this setting. In cases when there is a very busy enterprise server instance, the
sweep might cause MFCS to fall behind in task processing, causing a gradual drop in throughput. In this case, you can set
this to "no" to try to alleviate the problem.
Comments:
From Enterprise Server 7.0 Patch Update 2, performance of the mutex-sweep process has been improved. Micro Focus recommends that you do not use this setting to disable the mutex sweep. [2]
This sweep is a defensive measure that is typically performed at the end of each task. It checks to verify that the task does not end with any mutexes locked. A locked mutex at that point can only be the result of a logic error. The sweep ensures that such an error does not block the processing of any new requests.
Typically, it is not recommended to change this setting. In cases when there is a very busy enterprise server instance, the sweep might cause MFCS to fall behind in task processing, causing a gradual drop in throughput. In this case, you can set this to "no" to try to alleviate the problem.