[concurrency-interest] a question regarding the double-checkedlocking

David Holmes dcholmes at optusnet.com.au
Sun Jun 18 07:20:11 EDT 2006

I don't quite understand the static versus non-static parts of this. What
are "some object a" and "some object b" ?  A happens-before relationship
only occurs between an unlock and subsequent lock of a monitor on the same

But why would you bother even trying this when a single lock and making the
static instance volatile will work. Or even better use static
initialization, whether direct or via the static nested class idiom.

You have to ensure there is a happens-before relationship between the
construction of the instance, the writing of the instanace field ref and the
subsequent reading of it. I just described the minimal solution. There are
probably an unlimited number of strange things you could do to get the same

Don't know what you mean by "unify" nested locks. The compiler can't do
anything you could detect in the program as being incorrect.

David Holmes

 -----Original Message-----
From: concurrency-interest-bounces at cs.oswego.edu
[mailto:concurrency-interest-bounces at cs.oswego.edu]On Behalf Of Yechiel
Sent: Sunday, 18 June 2006 9:42 PM
To: concurrency-interest at cs.oswego.edu
Subject: [concurrency-interest] a question regarding the

  Hi all
  will the following double-checked locking code work ?
  note that when instance   is assigned a ref to the object, its after the
assigning thread have exited the inner synchronized block,
  so the ref dummy_instance must contain a completly initialized object
  If it works, will replacing the inner synchronized by a  dummy_instance
which is volatile do the job too ?
  Are there compiler optimizations which "unify" nested lockes ?

  private static Something instance = null;
  private  Something dummy_instance = null;

  public Something getInstance() {
    if (instance == null) {
      synchronized (some object A) {
          synchronized (some object B) {
            if (instance == null)
              dummy_instance = new Something();
          instance = dummy_instance;
    return instance;

-------------- next part --------------
An HTML attachment was scrubbed...
URL: /pipermail/attachments/20060618/2147e27f/attachment.html 

More information about the Concurrency-interest mailing list