Issue 3308: What happens to the existing transaction context on resume? (ots-rtf) Source: IONA (Mr. Derek Thomson, ) Nature: Uncategorized Issue Severity: Summary: According to the OTS spec, there is no guaranteed way to get the previous transaction back after calling Current::resume with another transaction. Current::commit and Current::rollback only restore the previous transaction context if the same thread started the transaction - otherwise the transaction context is set to null. This means that you might have lost the previous transaction that was replaced by "resume" ... or not, depending on where it was created. Is this desirable behaviour, considering that this suffers from the requirement to keep track of all the transactions ever created by each thread? Why not just restore the previous transaction context on commit and rollback? Resolution: Revised Text: Actions taken: February 10, 2000: received issue Discussion: End of Annotations:===== Sender: derek@ooc.com.au Message-ID: <38A236D5.A2A8D13E@ooc.com.au> Date: Thu, 10 Feb 2000 13:56:05 +1000 From: Derek Thomson Organization: OOC X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: ots-rtf@omg.org CC: issues@omg.org Subject: What happens to the existing transaction context on resume? Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: d4O!!Wda!!Kf\d9a>Sd9 According to the OTS spec, there is no guaranteed way to get the previous transaction back after calling Current::resume with another transaction. Current::commit and Current::rollback only restore the previous transaction context if the same thread started the transaction - otherwise the transaction context is set to null. This means that you might have lost the previous transaction that was replaced by "resume" ... or not, depending on where it was created. Is this desirable behaviour, considering that this suffers from the requirement to keep track of all the transactions ever created by each thread? Why not just restore the previous transaction context on commit and rollback? From: "Mark Little" To: "Derek Thomson" , Cc: References: <38A236D5.A2A8D13E@ooc.com.au> Subject: Re: What happens to the existing transaction context on resume? Date: Thu, 10 Feb 2000 10:02:51 -0000 Organization: Newcastle University MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Content-Type: text/plain; charset="iso-8859-1" X-UIDL: J3>!!//m!!bJ!!!(Obd9 ----- Original Message ----- > According to the OTS spec, there is no guaranteed way to get the previous > transaction back after calling Current::resume with another transaction. My reading of this has always been that the thread loses its old context in favour of the new one. There is no notion of it being able to go back. If the programmer wanted this behaviour then he could use suspend before resume. Mark. ----------------------------------------------------------------------- SENDER : Dr. Mark Little, Arjuna Project, Distributed Systems Research. PHONE : +44 191 222 8066, FAX : +44 191 222 8232 POST : Department of Computing Science, University of Newcastle upon Tyne, UK, NE1 7RU EMAIL : M.C.Little@newcastle.ac.uk Date: Wed, 1 Nov 2000 11:46:53 -0800 From: Blake Biesecker To: derek@ooc.com.au Cc: ots-rtf@omg.org Subject: Issue 3308 - What happens to the existing transaction context on resume? Message-ID: <20001101114653.D22222@gemstone.com> Mime-Version: 1.0 X-Mailer: Mutt 1.0pre4i X-Disclaimer: I only speak for myself, unless I expressly indicate otherwise. Content-Type: text/plain; charset=us-ascii X-UIDL: D9Z!!VZAe9XGWd9[_[!! Derek, What kind of changes to the OTS spec would you like to see to address your concerns? Blake Issue 3308: What happens to the existing transaction context on resume? (ots-rtf) Source: Object Oriented Concepts (Mr. Derek Thomson, derek@ooc.com.au) Nature: Uncategorized Issue Severity: Summary: According to the OTS spec, there is no guaranteed way to get the previous transaction back after calling Current::resume with another transaction. Current::commit and Current::rollback only restore the previous transaction context if the same thread started the transaction - otherwise the transaction context is set to null. This means that you might have lost the previous transaction that was replaced by "resume" ... or not, depending on where it was created. Is this desirable behaviour, considering that this suffers from the requirement to keep track of all the transactions ever created by each thread? Why not just restore the previous transaction context on commit and rollback? Resolution: Revised Text: Actions taken: February 10, 2000: received issue Discussion: