Advanced Java: Multi-threading Part 10 - Re-entrant Locks
HTML-код
- Опубликовано: 18 сен 2024
- More courses! Free C++ course: www.udemy.com/...
Make a social network with Spring Boot: www.udemy.com/...
Learn about MySQL and relational databases: www.udemy.com/...
Java desktop programming: www.udemy.com/...
Intermediate-Advanced C++ 11: www.udemy.com/...
-------------------------------------------------------------------------------------------------------------------------------------------
How to use the ReentrantLock class in Java as an alternative to synchronized code blocks. ReentrantLocks let you do all the stuff that you can do with synchronized, wait and notify, plus some more stuff besides that may come in handy from time to time.
--------------------------------------------------------------------------------------------------------------------------------------------
More videos on my RUclips channel: / caveofprogramming
John, I am revisiting these videos after 7 years because I am prepping for an interview. There is still that calmness, smoothness and ease of explaining complex topics simplistically. There are not many teachers like that, you are definitely one of the best. Cheers mate, keep up the good work.
me too can you tell me what all topics should I do after reentrant locks?
One of the best tutorials about threading I've ever seen. Greetings from Antarctica.
So you are one of those couple dozen people living in Antarctica? Are you a full resident or "summer only"?
So calm and smooth, I feel like I'm walking on the beach
Have commented before, elsewhere, but feel compelled to do so again, because to my mind there really is not enough I can say by way of 'thanks' for all this work you've put in to sharing your expertise. I work on Java every morning, hoping to make the career move to programmer one day (though it seems a long ways away), and your videos are a regular part of my routine. It's not just the content, it's the style that wins. It would hard take in this much info from an SME if they were not so 'listenable'. As a former teacher myself I truly appreciate your efforts.
*From the future* - Are you a java programmer now?
You have a fantastic, lucid way of explaining things. I have an exam tomorrow, these videos did a better job at making things clear than my entire shelf of Java books. That and the gorgeous Northern accent
One of the best tutorials about threading I've ever seen. Greetings from Winterfell.
You're quite right actually; I could have put the lock and unlock in increment(). Here it would have been better. There would be no side-effect for this code. I just wrote it the way I did because I thought it better illustrated the point I was making at the time.
great tutorial! one suggestion though, maybe edit out all the saliva sounds, they can be mildly distracting. Otherwise genuinely GREAT tutorial.
Thanks for the great tutorial! I was so happy when I heard your perfect English accent as opposed to all the other Indian videos, thanks for that too.
After thread2 call condition.signal(), thread 1's await () acquires the lock. So from this moment, which increment is executed firstly, 1 or 2?
Thank-You. Nice Explanation. I wonder why Reentrant locks exists at first place, but eventually u said @ last that we can try as well that could not be done with synchronized blocks.
the great teacher came out of a cave!! lovely lecture!!
Me imagining doing 100 lines of code in few minutes:
*Reality:* 4:46
Also, great video. Watching this in 2021 and it still is one of the best videos for learning threading. Greetings from India.
thank you for the quick response! got my exams in a week, this video helped alot :)
Thanks for the videos these are very informative and nicely deliverd. I have one query about the implementation of lock.lock() and lock.unlock().In the code base it's been used in both the method (firstThread and secondThread) ,instead of that can we use this locking and unlocking only in increment method. please verify and do inform if there is any side effect in this approach.which one would be more appropriate from performance perspective.
Thank you so much!! you can't imagine how much this video helped me!
Why do we need to put lock.wait()/unwait() separately in firstThread() and secondThread() ?
I think adding lock.wait/unwait() in increment() method will be enough.
I tested by implementing both scenarios, and the behaviour seems fine.
Anjali Chadha You mean await() :) There is no unwait. I'm on a limited Internet connection at the moment, so haven't watched the video to remind myself what's in it, but if I refer to the source code here: www.caveofprogramming.com/java-multithreading/java-multithreading-reentrantlock-video-tutorial-part-10.html there is no await() in secondThread(). The second thread just wakes up the first thread.
It re-acquires it automatically. await() is guaranteed not to return until the first thread can successfully re-acquire the lock.
After signaling we must call the unlock method, the other thread in awaiting state could get the lock again and move forward. thank a lot.
I don't know. Couldn't you only lock when you want to write, and not when you read? But you have to be careful that you don't read an inconsistent state.
Great tutorials - thank you! Using Blocking queues, I was able to simplify an old homework app which created a thread pool for a bank account from complex, hard-to-understand code to a trivial producer-consumer app as demonstrated in tutorial 7.
Regarding the question of how many locks to use; in this case, since Account is in-memory and not persisted (which is probably not a real-world scenario), I think it makes more sense to synchronize on the Account object's lock. This is a good demonstration of what lock does, but it also shows that it doesn't work in the same way as synchronized since you can't lock a specific object. What do you think?
Really good - just what I required explained to the point - Thanks.
You help me a lot with your tutorial. Thank you very much.
Thanks for the explanation!
Absolutely awesome videos on java multithreading concepts. I have finished almost all videos.
May be my question looks silly, but I need clarification.
None of your class didn't extends Thread class or didn't implements Runnable implements, then how the threads are running, is this because of the Java 8 Runnable functional interface.
It works, because he used Thread class, to create new Object. That Object implements Runnable interface, where body of run() method is defined within creating that object itself.
When you use use wait or await, when the other thread notifies or signals does the initial thread regain the lock or is it then waiting for the second thread to release the lock?
Both; when you use notify, the waiting thread "wakes up", but it can't actually get back the lock until the first thread releases it. As soon as it does, it gets the lock and continues past the wait statement.
you say that you have to unlock in the finally block when you signal, but when the first thread awakes, how does it get it's lock back then?
Why USE this if we have blockingqueue? Can blockingqueue be used instead
Thank you for providing those tutorials sir
Total count of 3 incorrect { at 4:45 had me screaming :D
oh man me too 1yr apart, same trigger
Awesome work man!! This is wonderful
U are awesome ... crystal clear .. love ur accent
Do you know how to use ReentrantReadWriteLock to allow multiple threads to read a collection, but when one thread is writing, no other threads can read or write. Thanks :)
Hi, Could you please provide the real time usages of ReentrantLock.. real time applications please?
another great video sir......
Really nice tutorial!
Great channel keep up with your great work :)
Part 10 why is the object of the Runner class made final in App Class?
Thanks for reply and clarification...!
thanks :) very clear explanation.
I run te same program but i never get anything othher tan 20k, but i added 3 more zeros and it showed different number less frewuently and higher the number it sows the same number less frequently.
Good luck!!
This is a excellent!
Thank you!
Hi,
I was using this code but not getting expected output. Can you please help me with this?
There are two files 1) Processor.java 2) App.java
Processor.java
package com.sujeettech.reenterantloack;
public class Processor {
private int count = 0;
private Object lock1 = new Object();
private Object lock2 = new Object();
void increment(){
count++;
}
void firstThread(){
synchronized(lock1){
for(int i = 0; i
Problem is that you are using 2 different object locks each thread having its own lock and proceeding with the execution in this case you shall not able to achieve mutual synchronization on same lock, may be you can use some thing like this,
class Processor {
private int count = 0;
private Object lock1 = new Object();
private Object lock2 = new Object();
void increment(){
//synchronized(lock2){
count++;
//}
}
void firstThread(){
synchronized(lock1){
for(int i = 0; i
Why Do we need two locks?
Sounds like this is how a sonic screwdriver works.
Thank you bro!
Wow, u bent Nederlands? U heeft dan een super goed Engels accent! :p
Nee, ik ben Engels, mar ik heb twee jar in Nederlands woonde (that's probably all wrong :) )
Cave of Programming Yes, it is a little (Nee, ik ben Engels, maar ik heb twee jaar in Nederland gewoond*) but it was clear what you were trying to say :p thanks for the tutorials by the way!
It must be cold in Antartica
Please, someone explain me the role the join method here. If I run my programm this way
th1.join();
//th2.join();
The count will be 2000
but if
//th1.join();
th2.join(); this way the result will be 1000
Why?????
Reason being u see difference in output is that, thread1 shall start incrementing the count variable only once thread2 completes, as it goes to await state statement "condition.await();" and waits for signal method to be called and lock to be released by thread2, by the time these happens thread2 already makes count value to 10000 and in finally block it releases lock, post this thread1 gets the lock back and calls increment method continues incrementing and end result of count becomes 20000.
Ok! this is rally weird.. because even without using the Lock. I get 2000! whats happening?
Funny how your pc is set in dutch while you have a perfect english pronounciation
Is it still relevant ??
the pop up message seemed like dutch to me..
I Love you !