• New Feature
  • Status: Open
  • 2 Major
  • Resolution:
  • DSO:L1
  • prodmgmt
  • Reporter: teck
  • June 12, 2006
  • 0
  • Watchers: 0
  • March 19, 2010


In the DSO code base we have the ability to extend the “volatile” field modifier to have a DSO semantic (ie. you can read/write volatile fields of shared objects w/o explicit locking). There is no user level way (ie. config element) to enable this behaviour though


Tim Eck 2007-04-06

I thought I had comments on this before. The more I thought about this the less I think we should do this :-)

From a completeness standpoint, it seems inconsistent to not promote volatile fields to have a DSO semantic, but I really think using volatile fields is way too fine grained for DSO use, but who ami I to say

orion 2007-04-06

I agree that it’s silly to expose volatile fields…

Fiona OShea 2007-09-27

Look at this during config rewrite

Howard Mak 2008-09-23

Terracotta complains (throws UnlockedSharedObjectException) when setting a volatile field in a DSO in the absence of any monitor locks. This makes it harder to clusterize code already optimized for non-Terracotta setups.

i.e., http://forums.terracotta.org/forums/posts/list/1336.page