Deadlocks vs Livelocks - Java Concurrency - Java Brains

preview_player
Показать описание
This video is from the full course:

In this video, you will learn about liveness, a property of software applications. You will also learn about deadlocks, livelocks and starvation, which are three possible causes of liveness in a concurrent program.
Комментарии
Автор

checkmate = deadlock
stalemate = livelock

simple way to remember thanks to this video

Altair
Автор

Javabrains is the best. Seriously I saw my first tutorial from this channel almost 6 years ago and after these much years it still contains new stuff for me. Tnx JavaBrains guys specially u, Koushik

seyedaliroshan
Автор

Nice analogies. Beautifully explained.

sujan_kumar_mitra
Автор

These information is very very important in real time.Thank you so much your effort

roshannandyala
Автор

Sir please create a video on Payment gateways in spring boot applications.

abhishekpatidar
Автор

@javaBrains I cant access the members only content after having the subscription .

vanishasingh
Автор

Hi Kaushik. Fantastic video! One suggestion I think you should come up with another section say "quick bytes" were videos are not more than 10mins.. Helpful for me to learn something quickly during travel to office or in loo 😂

indracharanpatil
Автор

Hi sir,
I'm very confused regarding learning MERN stack Or java backend(Spring & Spring boot) in terms of jobs and future prospective. Please please reply.

Ps-tpnu
Автор

Thanks man, I appreciate your work a lot!

molekuax
Автор

Do you have tutorial on multithreading?

tusharpawar
Автор

Java 8 added changes to threading, thread pool and future can you create a vid on this as I am addicted to your style of teaching <3

TomarSahab
Автор

Hi koushik sir..!
Have you ever had a deadlock situation when you coding for big projects?
If you have, how did you find it?

sandeepmreddy
Автор

What stack did you use to develop your website javabrains.io?

codegeek
Автор

is there any java brains video on the Future and Callable concept of Java?

TomarSahab
Автор

Isn't it like thread A waiting for resources which thread B is holding and thread B is waiting for resources which thread A is holding. Saying thread A waiting for thread B ? Is that correct ???

saswatsenapati
Автор

Analogies were ditto.
Soln is:~ java.util.concurrent.lock

SanjayKumar-byoc
Автор

I think your reference to circular locks is incorrect :
Java synchronized is 'reentrant' - meaning the same thread can enter synchronized methods on the same object any number of times. So if A object calls a method on B object which calls a method on C object which calls a method on the original A object, there will not be any deadlock *as long as the thread is the same*

sonyantony
Автор

Javabrains is the best. Seriously I saw my first tutorial from this channel almost 6 years ago and after these much years it still contains new stuff for me. Tnx JavaBrains guys specially u, Koushik

seyedaliroshan
join shbcf.ru