Bug #249

status variable should be at least volatile for synchronization purpose

Added by Stefano Lenzi about 4 years ago. Updated over 3 years ago.

Status:Closed Start date:07/11/2014
Priority:Low Due date:
Assignee:Stefano Lenzi % Done:


Category:zigbee.CC2530.driver Spent time: -
Target version:org.aaloa.zb4osgi.zigbee.CC2530.driver-0.3.0
Has a patch:No Has license agreement signed:No


Volatile [1,2] is a workaround for avoiding a synchronization block around all the access the state variable of the current Simple Driver implementation(s): namely DriverEZ430_RF2480 and DriverCC2530

See mailing-list thread at http://zb4osgi.aaloa.org/pipermail/dev/2014-July/000825.html

[1] - http://www.javamex.com/tutorials/synchronization_volatile.shtml
[2] - http://javarevisited.blogspot.it/2011/06/volatile-keyword-java-example-tutorial.html


Task #250: Backport bugfix for issue #249 from DriverCC2530 to Drive...ClosedStefano Lenzi

Related issues

related to Bug #244: Deadlock when reset dongle fails Closed 07/08/2014

Associated revisions

Revision 1041
Added by Stefano Lenzi about 4 years ago

Setting DriverState state variable as volatile ( refs #249 )


#1 Updated by Stefano Lenzi about 4 years ago

  • Description updated (diff)

#2 Updated by Stefano Lenzi about 4 years ago

  • Status changed from In Progress to Feedback

Set the variable as volatile, please test it and report your result

#3 Updated by Stefano Lenzi over 3 years ago

  • Status changed from Feedback to Closed
  • Target version changed from org.aaloa.zb4osgi.zigbee.CC2530.driver-1.X to org.aaloa.zb4osgi.zigbee.CC2530.driver-0.3.0

I will consider it as closed, please open it again if needed

Also available in: Atom PDF