CODEWITHSUNDEEP
javasynchronization
codefx
codefx

Reputation: 10512

What happens if synchronization variable is reassigned in java?

What happens in the following code? Does the synchronization work? This is an interview question.

class T
{
    public static void main(String args[])
    {
        Object myObject = new Object();
        synchronized (myObject)
        {
            myObject = new Object();
        } // end sync
    }
}

Upvotes: 5

Views: 558

Answers (6)

BIG NOSE
BIG NOSE

Reputation: 1

Run the Code And analyse the result.

public class Test {
    static Foo o = new Foo(0);
    static class Foo {
        private int i = 0;
        Foo(int i) {
            this.i = i;
        }
        public void addOnce() {
            this.i++;
        }
        public String toString() {
            return String.valueOf(i);
        }
    }
    public static void main(String args[]) {
        test1();
        try {Thread.sleep(10000);} catch (Exception e) {}
        test2();
    }
    public static void test1() {
        Runnable r = new Runnable() {
            public void run() {
                synchronized (o) {
                    System.out.println("1------>"+o);
                    o = new Foo(1);
                    try {Thread.sleep(3000);} catch (Exception e) {}
                    System.out.println("1------>"+o);
                }
            }
        };
        new Thread(r).start();
        new Thread(r).start();
    }
    public static void test2() {
        Runnable r = new Runnable() {
            public void run() {
                synchronized (o) {
                    System.out.println("2------>"+o);
                    o.addOnce();
                    try {Thread.sleep(3000);} catch (Exception e) {}
                    System.out.println("2------>"+o);
                }
            }
        };
        new Thread(r).start();
        new Thread(r).start();
    }
}

Upvotes: 0

Tiny Lin
Tiny Lin

Reputation: 258

You need obtain myObject's lock first,if this lock was blocked,you have to wait until the lock is released.

Synchronization requires multi-thread environment.But your code seems nothing to do with concurrent.So I am sorry to tell you that there is NOTHING going to happen.

Upvotes: 0

Peter Lawrey
Peter Lawrey

Reputation: 533660

Each time you enter the synchronized block, you synchronize on a different object. Most of the time this will not do anything except confuse you, but there is a small chance that two threads will see the same object and wait.

For this reason any code analysers will give you a warning if you are synchronizing on a field which is not final.

Upvotes: 4

MaVRoSCy
MaVRoSCy

Reputation: 17839

i don't see the reason behind this code since the Object is not shared by any threads. Removing the synchronized block will have no effect on the real outcome in any case. It will just make your code run faster

Upvotes: 0

Joonas Pulakka
Joonas Pulakka

Reputation: 36577

No, it doesn't work. Whenever a new thread comes in, a new myObject is created. Particularly now that myObject is a local variable!

It wouldn't work even if myObject is a class member since you would be changing the object you're locking on. See question about synchronization of non-final field for longer explanation.

Upvotes: 0

Jon Skeet
Jon Skeet

Reputation: 1502006

It still releases the same monitor that was acquired, but any other code which also locks using myObject (impossible here as it's a local variable, making the synchronization fundamentally pointless) would start to use the new object.

Don't forget that synchronization is applied to objects (or rather, the monitors associated with objects) - not variables. The monitor being acquired/released just depends on the value of the expression when the start of the synchronized block is reached. The expression is not re-evaluated at the end of the synchronized block.

Upvotes: 1

Related Questions