Session is already locked - Causes instability

[Ryszard@sfd.co]

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

Thank you for the suggestion, it was left as the default 30secs, I will try 0, the system is live so I won't know until restart this evening, and traffic lower over the weekend so it may be next week before results come in.