Description Julia Bremer 2024-01-03 10:22:02 CET

From time to time it happens that locking objects are left over.
Especially many were observed during support work in school environments.
It could be that the S4-Connector has part in it, but that is not clear yet. 

In one case, a customer had over 205000 left over temporary objects.

Those were copied to each server during the initial join process.
After deleting all of those objects, the join was 4-5 hours faster than before. 

We should examine how and why this happens, but most importantly enable the customer to clean those up safely.

I could imagine a diagnostic check with a "fix me" button that cleans up all locking objects that are older than a day or so.
Unfortunately the lockTime attribute does not have the appropriate matching rule to search for a timestring older/eq a certain value. I had to use createTimestamp instead.