[progress Communities] [progress Openedge Abl] Forum Post: Re: What Are Very Large Latch Ids?

[George Potemkin]

BTW, does anybody know how Progress calls these (sub-)latches of the governing latches (BUF and LKT)? Progress seems to use the latObjLatchLock() call to lock the multiplexed latches of the BUF latches - Buffer Control Blocks latches. The article 000035040 seems to call them the object latches: knowledgebase.progress.com/.../000035040 " Upgrade to OpenEdge 10.2B08, 11.3.0.0 or later where the problem of the process not in service when executing a critical session on the object latches has been addressed ." latObjLatchFree: owner %d of object latch %i is not me (lockCnt: %i, addr: %x) latch stack: %d latObjLatchLock2: latchNum: %l, (lockCnt: %i, addr: %x) latch stack: %d latches: %x latObjLatchLock being called with a latch other than a lock table chain latch But they do not seem to be the same as the Object Number Latches introduced in 11.6: User died holding the Object Number Latch. (18115) "Object Number Latch" seems to be one of the "service" (?) latches like: BIADD Latch AI Mgt Latch XAlist Latch DB Service Latch Large Keys Enablement Latch Audit Policy Latch Object Number Latch Audit Latch SQLTSINFO Latch REPL EOF Latch Progress seems to use the pmObjectLockLock call to lock the multiplexed latches of the LKT latches (called "LHT" in _Latch VST) - Lock Table Hash Chain latches (introduced in 10.0A). 10.2B06 Service Pack Readme seems to call them the private latches: knowledgebase.progress.com/.../fileField " Replication server can get blocked on private latch in pmObjectLockLock() when more than 1 remote SQL user is connected to a SQL92 remote server ." Do the new messages introduced in V11 talk about the same private latches? 11.0: SYSTEM ERROR: User died holding the latch. (15767) Desc: The user has died while holding a private latch. 11.6: User died holding the . (18386) Desc: User with usernum died holding a private latch as specified. Just curious as always.

Continue reading...