-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
---
-
---
-
Currently if there is any logic that could break the lock/unlock exception it might leave the system unusable. This jiras tries to tackle that trying to detect when that happens based on automatic detection so the system can continue to work.
This is the continuation of work in JBPM-9521
Added new lock implementation that allows to unlock from another thread
org.jbpm.runtime.manager.impl.lock.SelfReleaseRuntimeManagerLock
Also I created a thread watcher attached to every runtime Manager that spawns a thread to watch every lock for a runtime manager.
Two environment variables has been created
org.kie.jbpm.lock.polling
if equals to zero then it does not activate polling. greater to zero will check every interval if those locks have exceeded the maximum processing time.
The maximum processing time is the max time a lock is considered that is not unlocked.
org.kie.jbpm.lock.maxProcessingTime
- is related to
-
JBPM-9521 Provide runtime manager strategies and lock diagnose upon system lock broken mecahnism
- Resolved
- relates to
-
RHPAM-3391 Provide runtime manager strategies and lock diagnose upon system lock broken mechanism
- Closed