Question
Tata Consultancy Services
IN
Last activity: 27 Nov 2023 23:25 EST
LockCacheImpl
Hi,
In our application, we are getting the below error sometimes. Can someone help what can be the reason and how we can fix it?
2022-12-01 10:27:03,596 [http-nio-8829-exec-7] [TABTHREAD0] [ ] [Application:01.01.01] ( internal.lock.LockCacheImpl) ERROR .....| Proprietary information hidden XXXXXX65 - Existing entry overwritten for ORG-WORK-APP W-123
***Edited by Moderator Marije to add Capability tags***
LTIMindtree
SA
Please elaborate and add the necessary screenshots of the issue of when and what occasions did you observe the error?
societe generale
IN
These logs seems to be from deferred queue .Where some entries seems be processed after work object has been modified/deleted. Try using commit method after action on work object . So that deferred queue entries for the case will be cleared .
Bits in Glass
CA
@avisekmondaldid you found solution for this? we are also facing this while importing new zip to our QA environment.
Natwest
GB
@avisekmondal Any solution found for this please? Facing same issue
Coforge
IN
Could you tell the scenario/steps where you are facing the issue
Updated: 27 Mar 2023 7:20 EDT
Natwest
GB
@abhiraj Its a bit random. Not happening for every user all the time and could not narrow down a specific user action causing this. Logs suggest that its happening for background processing as well.
2023-03-27 10:10:44,757 [asterQueueProcessors] [ STANDARD] [ ] [ ] ( internal.lock.LockCacheImpl) ERROR B1S5CIHL38JD37Q5G32CMA7UVLVXS0YXVA - Existing entry overwritten for MyOrg-Test-Work AB123
2023-03-27 09:09:52,556 [tp-nio-8080-exec-170] [ STANDARD] [ ] [ Test:02.09] ( internal.lock.LockCacheImpl) ERROR <hostname> H5YL7SXT9VYM62UIOGZYE3JC42DLD2XVVA <username> - Existing entry overwritten for MyOrg-Test-Work AB123
2023-03-27 08:54:23,564 [S-MasterJobScheduler] [ STANDARD] [ ] [ ] ( internal.lock.LockCacheImpl) ERROR BI2R9ITQ6OX7AGGRL2Z6MUVI1YCNWTZ5PA - Existing entry overwritten for MyOrg-Test-Work AB123
Updated: 27 Mar 2023 8:40 EDT
Coforge
IN
Can you tell which type of locking strategies you have for this case type?
Default locking (allow one user) or optimistic(Allow multiple users) locking?
Updated: 28 Mar 2023 5:52 EDT
Coforge
IN
As you have default locking, if one requestor (either user or background job) has acquired the lock and before it get released other requestor tries to acquire lock or save the instance, such lock issue may occur.
Can you try once for one casetype by changing the locking strategy to optimistic (Allow multiple users), see if you are still getting the same issue.
If changing the locking strategy solves your issue & you still want to go with default. Try avoiding updating same work object by different requestors if it is locked by others.