[OPNFLWPLUG-840] Openflow Transaction Manager wrapper does not handle synchronization properly Created: 10/Jan/17  Updated: 27/Sep/21  Resolved: 30/Mar/17

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jon Castro Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7500

 Description   

TransactionChainManager implementation uses synchronization to guarantee that clients are able to perform modifications and submit actions in a transaction chain that is unique at a given point of time. Also, the creation of the transaction chain is hidden and the transaction is created by the first client that tries to add a modification the first time or after a submit.

There are few bugs in the code of this class which above promise is not guaranteed.

  • wTx variable does not handles the reference to the current transaction properly in all cases
  • lifecycle is closed when an exception is returned by MD-SAL that commonly could happen
  • synchronization is not implemented properly to guaranteed there is only one transaction open at a given point of time


 Comments   
Comment by Jon Castro [ 30/Jan/17 ]

https://git.opendaylight.org/gerrit/#/c/50153/

Comment by Robert Varga [ 28/Mar/17 ]

master: https://git.opendaylight.org/gerrit/52965

Generated at Wed Feb 07 20:33:31 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.