This method is correct and should be used:
public synchronized double withDrawFromPrivateBalance(double a)
{
balance -= a;
return balance;
}
It correctly restricts access to the account internal state to only one thread at a time. However your balance
field is public
(so not really internal), which is the root cause of all your problems:
public double balance = 1500;
Taking advantage of public
modifier you are accessing it from two threads:
private synchronized void find(){
localBalance = myTargetAccount.balance;
System.out.println(getName() + ": local balance = " + localBalance);
localBalance -= 100;
myTargetAccount.balance = localBalance;
}
This method, even though looks correct with synchronized
keyword, it is not. You are creating two threads and synchronized
thread is basically a lock tied to an object. This means these two threads have separate locks and each can access its own lock.
Think about your withDrawFromPrivateBalance()
method. If you have two instances of Account
class it is safe to call that method from two threads on two different objects. However you cannot call withDrawFromPrivateBalance()
on the same object from more than one thread due to synchronized
keyword. This is sort-of similar.
You can fix it in two ways: either use withDrawFromPrivateBalance()
directly (note that synchronized
is no longer needed here):
private void find(){
myTargetAccount.withDrawFromPrivateBalance(100);
}
or lock on the same object in both threads as opposed to locking on two independent Thread
object instances:
private void find(){
synchronized(myTargetAccount) {
localBalance = myTargetAccount.balance;
System.out.println(getName() + ": local balance = " + localBalance);
localBalance -= 100;
myTargetAccount.balance = localBalance;
}
}
The latter solution is obviously inferior to the former one because it is easy to forget about external synchronization somewhere. Also you should never use public fields.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…