What is a Livelock scenario in java?

Image by Clker-Free-Vector-Images from Pixabay

Livelock is a scenario in which two or more block each other by responding to an action caused by another thread.

In a deadlock situation, two or more threads wait in one specific state.

In a Livelock scenario, two more threads change their state in such a way that it prevents progress on their regular work.

E.g. Consider a scenario in which two threads try to acquire two locks.

They release a lock that they have acquired when they cannot acquire the second lock.

In a Livelock situation, both threads concurrently try to acquire the locks.

Only one thread would succeed, the second thread may succeed in acquiring the second lock.

Now both threads hold two different locks. And both threads want to have both locks.

So they release their lock and try again from the beginning. This situation keeps repeating multiple times.

Comments

Defination of the essential properties of operating systems

Define the essential properties of the following types of operating sys-tems: Batch Interactive Time sharing Real time Network Parallel Distributed Clustered Handheld ANSWERS: a. Batch processing:- Jobs with similar needs are batched together and run through the computer as a group by an operator or automatic job sequencer. Performance is increased by attempting to keep CPU and I/O devices busy at all times through buffering, off-line operation, spooling, and multi-programming. Batch is good for executing large jobs that need little interaction; it can be submitted and picked up later. b. Interactive System:- This system is composed of many short transactions where the results of the next transaction may be unpredictable. Response time needs to be short (seconds) since the user submits and waits for the result. c. Time sharing:- This systems uses CPU scheduling and multipro-gramming to provide economical interactive use of a system. The CPU switches rapidl

What is a Fair lock in multithreading?

Photo by João Jesus from Pexels In Java, there is a class ReentrantLock that is used for implementing Fair lock. This class accepts optional parameter fairness. When fairness is set to true, the RenentrantLock will give access to the longest waiting thread. The most popular use of Fair lock is in avoiding thread starvation. Since longest waiting threads are always given priority in case of contention, no thread can starve. The downside of Fair lock is the low throughput of the program. Since low priority or slow threads are getting locks multiple times, it leads to slower execution of a program. The only exception to a Fair lock is tryLock() method of ReentrantLock. This method does not honor the value of the fairness parameter.

Windows Azure Video

Make a Free Website at Wix.com Tweet

CODING PUSH

Search This Blog