Skip to main content

Thread Basics

Thread Basics


1-      Thread Creation :
There are two ways of creating a new thread.

Way-1 Implementing Runnable Interface:
public class CustRunnable implements Runnable {

    public void run() {
        System.out.println("Executed !");
    }

    public static void main(String args[]) {
        Thread myThread =  new Thread(new CustRunnable());
        myThread.start()
    }
}

Way-2 Extending Thread Interface:
public class CustThread extends Thread {

    public void run() {
        System.out.println("Executed from a new thread!");
    }

    public static void main(String args[]) {
        CustThread myThread = new CustThread();
        myThread.start();
    }
}

First way is preferable. Because it leaves the flexibility of extending another class and compatible with higher level thread management APIs.
2 -      Important Thread Methods

-    public static void sleep(long millis) throws InterruptedException

public static void sleep(long millis, int nanos) throws    InterruptedException

Executing threads goes to sleep for specified times amount. Puts thread into TIMED_WAITING state. Thread doesn’t leave locks it obtains. If thread is interrupted during sleep, InterruptedException is raised.

-          public void interrupt()

Used to interrupt a thread. When a thread is interrupted it stops what it is doing and does some thing in respose to interrupt.

Generally threads respond to interrupts by stopping execution. A typical respond is as in the example.

public void run() {
        try {
            Thread.sleep(10000);
        } catch (InterruptedException e) {
            return;// stop execution
        }
      }

Thread related methods tend to throw InterruptedException. If a thread is not invoking a method that throws InterruptedException, a thread my check interrupt status by calling Thread.interrupted()method.
·         Remember after throwing InterruptedException or returning true to static Thread.interrupted() method, thread’s internal interrupt status flag is cleared.
·         The non-static version of interrupted() method doesn’t clear interrupt status flag.

-          public final void join() throws InterruptedException

public final void join(long millis) throws InterruptedException

public final void join(long millis,int nanos) throws InterruptedException

Allows a thread to pause execution until another thread finishes execution. Puts  thread into WAITING state. Overloaded versions allows to specfy a timeout value and puts thread into  TIMED_WAITING state.


May throw InterruptedException .

Comments

Popular posts from this blog

Obfuscating Spring Boot Projects Using Maven Proguard Plugin

Introduction Obfuscation is the act of reorganizing bytecode such that it becomes hard to decompile. Many developers rely on obfuscation to save their sensitive code from undesired eyes. Publishing jars without obfuscation may hinder competitiveness because rivals may take advantage of easily decompilable nature of java binaries. Objective Spring Boot applications make use of public interfaces, annotations which makes applications harder to obfuscate. Additionally, maven Spring Boot plugin creates a fat jar which contains all dependent jars. It is not viable to obfuscate the whole fat jar. Thus obfuscating Spring Boot applications is different than obfuscating regular java applications and requires a suitable strategy. Audience Those who use Spring Boot and Maven and wish to obfuscate their application using Proguard are the target audience for this article. Sample Application As the sample application, I will use elastic search synch application from my GitHub repository.

Hadoop Installation Document - Standalone Mode

This document shows my experience on following apache document titled “Hadoop:Setting up a Single Node Cluster”[1] which is for Hadoop version 3.0.0-Alpha2 [2]. A. Prepare the guest environment Install VirtualBox. Create a virtual 64 bit Linux machine. Name it “ubuntul_hadoop_master”. Give it 500MB memory. Create a VMDK disc which is dynamically allocated up to 30GB. In network settings in first tab you should see Adapter 1 enabled and attached to “NAT”. In second table enable adapter 2 and attach to “Host Only Adaptor”. First adapter is required for internet connection. Second one is required for letting outside connect to a guest service. In storage settings, attach a Linux iso file to IDE channel. Use any distribution you like. Because of small installation size, I choose minimal Ubuntu iso [1]. In package selection menu, I only left standard packages selected.  Login to system.  Setup JDK. $ sudo apt-get install openjdk-8-jdk Install ssh and pdsh, if not already i

Java: Cost of Volatile Variables

Introduction Use of volatile variables is common among Java developers as a way of implicit synchronization. JIT compilers may reorder program execution to increase performance. Java memory model[1] constraints reordering of volatile variables. Thus volatile variable access should has a cost which is different than a non-volatile variable access. This article will not discuss technical details on use of volatile variables. Performance impact of volatile variables is explored by using a test application. Objective Exploring volatile variable costs and comparing with alternative approaches. Audience This article is written for developers who seek to have a view about cost of volatile variables. Test Configuration Test application runs read and write actions on java variables. A non volatile primitive integer, a volatile primitive integer and an AtomicInteger is tested. Non-volatile primitive integer access is controlled with ReentrantLock and ReentrantReadWriteLock  to compa