Tools
Sign in
Login
Forum
com.nm.utils.locking.LockException: Timeout waiting for lock
Forum
>
Extensions
>
com.nm.utils.locking.LockException: Timeout waiting for lock
n/A
posted
on April 23, 2015
at 3:07 PM
Version
5.3.11
n/A
posted
on April 23, 2015
at 3:07 PM
Version
5.3.11
Hi We are getting this exception one of our environment. Same code on another environment is working fine.
Could you please me know what could be wrong ?
com.nm.utils.locking.LockException: Timeout waiting for lock
Resource = 1429736934348
Owner = 110
Count = 1
Created = 2015-04-23 09:01:10
Modified = 2015-04-23 09:01:10
Lock Thread:
Name = http-7070-10
Id = 110
State = RUNNABLE
n/A
replied
on April 29, 2015
at 5:20 PM
n/A
replied
on April 29, 2015
at 5:20 PM
Hi Mahesh,
that exception normally is a warning to let you know that a process instance was locked for a long time while another thread tried to acquire the lock on it. On 5.3.11 this second thread would wait until a certain timeout expires and then throw this exception.
The most common case where this happens is when you have a process instance that calls a very long running script task. In case the script execution is triggered by a user interaction, like the user clicks on the "next" button in the process, then the http thread in charge of serving the user request will execute also the slow script evaluation. Until the script evaluation is completed the process instance is locked. In appway 5.3 there is a job that takes care of persisting all the process instances every 5 minutes. If your instance is locked while the job runs you get the warning above.
If you are in the situation I described you probably don't have anything to worry about, apart from the slow script itself. If you have another case, meaning the thread accessing the instance is of another kind, or you have any other locking related incident, it is probably worth analyzing the case by using the Studio > Console > Process Engine > Process Locks tab.
Cate
replied
on May 7, 2015
at 9:58 AM
Cate
replied
on May 7, 2015
at 9:58 AM
Hi Mahesh,
Have you managed to resolve the issue with the exception?
Cate
n/A
replied
on May 12, 2015
at 2:53 PM
n/A
replied
on May 12, 2015
at 2:53 PM
Hi Cate
Yes, as Mauro explained we were able to resolve this issue. One of our third party application web service was taking time to respond.
Thank You Mauro.
Please
sign in
to add a reply
About this site
|
Terms of use
|
Privacy statement
|
Contact us
© 2025 Appway AG. All Rights Reserved.
Could you please me know what could be wrong ?
com.nm.utils.locking.LockException: Timeout waiting for lock
Resource = 1429736934348
Owner = 110
Count = 1
Created = 2015-04-23 09:01:10
Modified = 2015-04-23 09:01:10
Lock Thread:
Name = http-7070-10
Id = 110
State = RUNNABLE