Question about TransactionMgr

Brought to you by: amy_murphy, gpietro

Question about TransactionMgr

Forum: Open Discussion

Creator: Chien-Liang Fok

Created: 2002-08-08

Updated: 2002-08-19

Chien-Liang Fok - 2002-08-08

Lines 1617 - 1618 of TransactionMgr has the following:

|| (desc.transType == AGENT_BYE &&
!allTSUniform(currentInitiatedTrans.lts, true)

It appears to be rejecting the initiator's transaction if the transaction is an agent disengagement and at least one of the agent's tuple spaces is not shared.

Why do all of the initiating agent's tuple spaces need to be shared in order for it to disengage?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Amy Murphy - 2002-08-19
  
  The reasonsing was that the operation setShared is called with either the boolean true (meaning to set shared) or false (meaning to remove from sharing). So, if you pass an array of tuple spaces, then they should all be changing from not shared to shared or from shared to shared.
  
  If you sent some which were shared and some which were not shared, then you made a mistake, and the transaction should be aborted.
  
  At least this is the best explanation I can provide without delving into the details. Hope it helps.
  
  -amy
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.