[CONTROLLER-803] Clustering : Evaluate using AtomicBoolean instead of synchronization in DataChangeListenerRegistrationProxy Created: 10/Sep/14  Updated: 19/Oct/17  Resolved: 03/Oct/14

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
Fix Version/s: None

Type: Bug
Reporter: Moiz Raja Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: PC


External issue ID: 1795

 Description   

see https://git.opendaylight.org/gerrit/#/c/10891



 Comments   
Comment by Tom Pantelis [ 11/Sep/14 ]

We have 2 variables in play here, closed and listenerRegistrationActor. The sync block is needed for atomicity to guarantee we only send one close message to the actor. I don't think we would be able to do that with just an AtomicBoolean and CAS (unless I'm missing something).

Generated at Wed Feb 07 19:53:55 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.