[Progress Communities] [Progress OpenEdge ABL] Forum Post: RE: Concurrent record locks are withheld from client/servers sessions for an excessive amou

Status
Not open for further replies.
D

dbeavon

Guest
The "FIRST" wasn't relevant and I removed it for now. 2) The Nmsgwait was already 1. Out of curiousity I bumped that up to 4 and things get a lot worse than before (especially in PASOE since the max lock wait time is 10 seconds, and all five sessions aren't able to get a record lock anymore in that limited amount of time.) Here is the new output from my original code, as five sessions simultaneously start executing at the same time. [18/12/14@13:02:25.041-0500] P-004464 T-029728 1 AS-7 APPL Lock Wait Times 103 103 [18/12/14@13:02:31.064-0500] P-004464 T-014696 1 AS-6 APPL Lock Wait Times 6105 6124 [18/12/14@13:02:34.946-0500] P-004464 T-029636 1 AS-8 -- (Procedure: 'GetData app/Production/Maintenance/Kiln/AppServer/KilnTesting.p' Line:64) Lock wait timeout of 10 seconds expired (8812) [18/12/14@13:02:34.966-0500] P-004464 T-022712 1 AS-4 -- (Procedure: 'GetData app/Production/Maintenance/Kiln/AppServer/KilnTesting.p' Line:64) Lock wait timeout of 10 seconds expired (8812) [18/12/14@13:02:34.987-0500] P-004464 T-028988 1 AS-9 -- (Procedure: 'GetData app/Production/Maintenance/Kiln/AppServer/KilnTesting.p' Line:64) Lock wait timeout of 10 seconds expired (8812) It seems that this Nmsgwait is the parameter that controls how long it takes for sessions to detect that a lock was released. It is very unfortunate that this is measured seconds rather than milliseconds... I suppose that means I have to just use my NO-WAIT looping strategy.

Continue reading...
 
Status
Not open for further replies.
Top