Process Locks

[Matt_Leonard3]

Is there a way to check for Process Locks that are old/stale and remove them via scripting?

We have a Workflow Timer Unity Script process that calls a custom external DLL and has memory leaks so it crashes the entire Workflow Timer service intermittently.  As a work around, we have cleaned up everything except for the process lock it leaves behind.  Is there any way we can clean that up programmatically?

Thank you,

Matt Leonard

[Daniel_Quill]

Unfortunately, none of the OnBase APIs have the ability to check or remove process locks.

[Robert_Davies]

We have the same problem as Matt above. Does your answer still stand 4 years on from the original question?

[Daniel_Quill]

This is still valid. There is no method for checking process locks. The API only supports validating Document locks. Working with process locks are not supported.

[Amy_Young-Leith]

What do most caretakers of OnBase do to manage this? What's a good practice, like reviewing X often, and removing locks more than Y old?

In digging into some transient and hard to reproduce issues we have, I've found that we have a lot of document locks (1408 going back to3/27/17) and process locks (408 going back to 1/18/17).