Skip to main content

Atomic operation and classes in the Java Concurrency API:

Atomic Operation and Class:

An operation is classified as atomic if it is performed as a single unit of work without the possibility of interference from other processes.

In the Java language specification, they guarantee that the reading or writing operation is atomic (unless the variable is a long or a double). Variables of type long or double in operations are only atomic if declared with the keyword: volatile.


Suppose we assume that i is defined as an int. The i++ (increment) operation is not an atomic operation in Java. This also applies to the other numeric types, e.g. long. This is because the i++ operation first reads the value currently stored in i, and then it adds one to it. However, between the read and the write, the value of i might have changed.


Since Java 1.5, the java language provides an atomic class with variables such as AtomicInteger or AtomicLong. The class also provides methods like getAndDecrement(), getAndIncrement() and getAndSet() which are all atomic. Using these provides that atomic guarantee.

Popular posts from this blog

What happens if we don't override the run() method:

Consequences of not overriding the run() method: If we don’t override the run() method, the compiler will not flash any error, and it will execute the run() method of the Thread class that has been emptily implemented, So, there will be no output for this Thread. Below is an example of the method returning no output: public class Example extends Thread { public static void main(String[] args) { Thread thread = new Thread( new Example()); thread.start(); // will create a new thread and call thread class's run() method which has no implementation. } }

Creating and Running a Java Thread:

Ways to create a Thread: You can create a Thread in two ways: By extending the Thread class. By implementing a Runnable Interface. Thread class: The Thread class provides constructors and methods to create and perform operations on a thread. Runnable Interface: Runnable Interfaces have only one method,  named run() . The Runnable Interface should be performed by classes where their instances plan to be executed by a thread.  public void run() : is used to perform the action for a Thread. Starting a thread: The  start() method  of a Thread class is used to start a newly created thread. It performs the following tasks: A new thread starts(with their stack). The Thread moves to the Runnable state from New state. The  run() method  will run when the Thread gets a chance. Java Thread Example by extending Thread class: class  Multi  extends  Thread{   public   void  run(){   System.out.println( "Extended Thread Class E...

Concurrent Collection Classes:

Concurrent Collection Classes: Java utility classes are generally useful when used with concurrent programming. This package includes a few small standardized extensible frameworks and some classes that provide proper functionality that is otherwise very difficult to implement. Concurrent Collections: This package supplies Collection implementations mainly used in multithreaded processes.  A concurrent collection is always  thread-safe , and a single exclusion lock does not govern it. Here are some of the classes below: ConcurrentSkipListMap:  Usually preferable to a synchronized TreeMap CopyOnWriteArraySet:  Well suited for applications where set sizes generally stay small and read-only operations vastly outnumber mutative operations(add, set, remove, etc.). ConcurrentSkipListSet:   This is essentially an equivalent of TreeMap and TreeSet for concurrent code. CopyOnWriteArrayList:  It’s preferable over synchronized ArrayList, where an expected number of re...