AtomicInteger
works with two concepts : CAS and volatile
variable.
Using volatile
variable insures that the current value will
The atomic objects make use of Compare and Swap mechanism to make them atomic - i.e. it is possible to guarantee that the value was as specified and is now at the new value.
The code you posted continually tries to set the current value to one more than it was before. Remember that another thread could also have performed a get
and is trying to set it too. If two threads race each other to change the value it is possible for one of the increments to fail.
Consider the following scenario:
get
and gets the value 1
.next
to be 2
.get
and gets the value 1
.next
to be 2
.Now because of atomics - only one thread will succeed, the other will recieve false
from the compareAndSet
and go around again.
If this mechanism was not used it would be quite possible for both threads to increment the value resulting in only one increment actually being done.
The confusing infinite loop for(;;)
will only really loop if many threads are writing to the variable at the same time. Under very heavy load it may loop around several times but it should complete quite quickly.
for (;;)
is an infinite loop, so it will just retry the attempt.