Issue 578: Who is responsible for releasing locks in transaction? (concurrency) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: In lock duration of Section 7.1 there are two descriptions. The role of the clients is vague to me Resolution: Revised Text: Actions taken: May 20, 1997: received issue Discussion: End of Annotations:===== Return-Path: From: KENJI.KUSHI@soft23.soft.soft.hitachi.co.jp Message-Type: Multiple Part Subject: CosConcurrency questions To: concurrency@omg.org Sender: KENJI.KUSHI@soft23.soft.soft.hitachi.co.jp Date: Tue, 20 May 97 18:26:02 +0900 Content-Identifier: X Priority: normal Importance: normal X400-Received: by /C=JP/ADMD=HITNET/PRMD=HITACHI/; deferred until Tue, 20 May 97 18:26:02 +0900; Relayed; Tue, 20 May 97 18:26:02 +0900 X400-Mts-Identifier: [/C=JP/ADMD=HITNET/PRMD=HITACHI/;SOFT23970520183434CZU] X400-Originator: KENJI.KUSHI@soft23.soft.soft.hitachi.co.jp X400-Recipients: concurrency@omg.org X400-Content-Type: (22) Regarding the CosConcurrency specification(Feb 12 97), I have three questions. 3. Who is responsible for releasing locks in transaction ? In "lock duration" of Section 7.1, there are two descriptions "Using the two phase commit protocol,locks held by a transaction are automatically dropped when the transaction completes" and "It is up to clients of the concurrency control service to associate lock sets together and to release the locks when a transaction commits or aborts." The role of the clients is vague to me. Best regards. --Kenji Kush