07-09-2020, 11:49 PM
(This post was last modified: 07-09-2020, 11:55 PM by Alexandre Machado.)
Besides that, seems that the session lock timeout value is too small for you. Are you using the default timeout value (in older versions it could be like 30 seconds).
If you have processes that can take more time, please consider increasing it.
BTW, if you set it to ZERO, you will never see such errors again. New requests will be put on hold until the first is responded. They will be responded one by one sequentially later.
The property is ServerController.SessionOptions.LockSessionTimeout
If you have processes that can take more time, please consider increasing it.
BTW, if you set it to ZERO, you will never see such errors again. New requests will be put on hold until the first is responded. They will be responded one by one sequentially later.
The property is ServerController.SessionOptions.LockSessionTimeout