Deadlocks vs Livelocks - Java Concurrency - Java Brains 

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

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

Thanks so much koushik

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 😂

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

superb...

Nice analogies. Beautifully explained.

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.

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

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

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

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 ???

Do you have tutorial on multithreading?

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

Thanks for the amazing content

Livelock example , hahahaha

K thanks man

First ❤️

Thank you!

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

Thanks man, I appreciate your work a lot!

Solid material! Thank you

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

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*

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

Your analogies are very helpful.