0

Is it possible for the thread scheduler to unschedule a thread holding the lock to a synchronized block and is in the middle of executing it? If yes then does the unscheduling leads to thread releasing the lock? Assume thread doesn't call method such as wait/yield etc.

I have been trying to understand how synchronized block helps in read-update-write operation? If the thread which enters the synchronized block can't be unscheduled then it's easier to understand but if it can be then the issue of visibility comes as it might be the case that variable has been updated but not written to the main memory by thread and thread scheduler unschedules it and other thread gets the lock and updated the variable in the main memory. Is there any info. in JLS regarding the same?

Yug Singh
  • 3,112
  • 5
  • 27
  • 52
  • "The thread scheduler" typically obeys a _[scheduling discipline](https://en.wikipedia.org/wiki/Scheduling_(computing)#Scheduling_disciplines)_ (a.k.a., _scheduling algorithm_), from which there are many to chose. In some operating systems, the scheduling discipline may be configurable, may be changed at run-time, and/or may be different for different thread/process groups. – Solomon Slow Jan 08 '19 at 22:18

1 Answers1

3

Is it possible for the thread scheduler to unschedule a thread holding [a lock]?

Yes, that can happen preemptively in many scheduling algorithms. It must happen if the thread makes a blocking system call (e.g., to wait for input).

If yes then does the unscheduling leads to thread releasing the lock?

Absolutely not! That would defeat the purpose of locking, and it would break most multi-threaded programs.

Takeaway: Keep your critical sections as short as possible! Don't let threads B, C, D, and E all get blocked waiting for thread A to release some lock when thread A is blocked performing a long computation (or worse, waiting for input).

Solomon Slow
  • 25,130
  • 5
  • 37
  • 57