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

[Brendan_Altman2]

@Daniel
This sounds like a great enhancement request for API to have the ability to remove process locks 🙂

[Marc_Campbell]

@Amy, we (try to) check the locks every day and remove any that are more than 24 hours old. Of course if the lock is still an active process, we let it be. Generally, the active locks get cleared up either by us or on their own after a few days. If not, we just kind of wing it. "The process has been there for a week. Ok, we're probably safe killing it."

[Kevin_Perron]

Since going to V 17.1 we have an increase in the number of locks and a lot of them are related to working with documents in a Scan Queue. We manually clear out hundreds of locks on a daily basis now. Not exactly a new daily task I was hoping for our team to have to do!
-KP

[Daniel_Quill]

Kevin,
Can you provided some additional information around the increased number of locks that you are experiencing? Can you tell us what version of OnBase you upgraded from? Also, what is the process flow in which the locks are occurring? You technically should not be getting locks much or at all.

We would like to assist further to define the cause of the issue and possibly correct/minimize it and reduce the manual process of clearing the locks.

It may be worth contacting your first line of technical support to begin investigating in more detail.

Thanks,

[Lou_Trenka]

We do redundantly remove a small amount of process and Document locks on a daily basis in our current version (15.0.2) and when we do we are often prompted with

" is no longer a connected user so this lock does not appear to be active.
Are you sure you want to remove this lock?"....Sure I do!

An enhancement request to (at a minimum) clear these types of locks or at least a global administrative choice to remove user owned locks when a user logs out of the system would be something we would happily sign up for. We are planning an upgrade to 17 and I do not like the reports of potentially more locks.

@Kevin...are your users using the Unity client scanning or Thick?