Java & threads: interrupted exceptions and the correct use of the BlockingQueue take () method

Question

What exactly happens when there is nothing in the queue and the take () function is called. The API says that the method will wait, but does this mean that the processor rotates checking empty / non-empty until the element is in the queue, or does it mean that the thread is giving and will be woken up by an interrupt? If so, then I probably want to see that the queue is empty, and if it is a call to thread.yield (), to give up CPU time. My question is, do I really need to generate revenue or is some kind of internal mechanism processing this for me?

Secondly, what is the interrupted exception intended for? If I understand correctly, this means that if thread A executes this method and expects input, and another thread B calls threadA.interrupt (), then thread A will catch the thrown exception and suspend execution if it is good. Is this the right way to think about it?

Answer 1

Note that BlockingQueue is an interface. So what follows the implementation. If you look at the source code for (say) LinkedBlockingQueue , the source for take () calls lockInterruptibly () in RentrantLock. From the doc for this:

, :

* The lock is acquired by the current thread; or
* Some other thread interrupts the current thread, and interruption of

.

, wait()/notify() . ? ( top )

Re. , Java Specialist interrupt() / InterruptedException.

, , , :

  try {
        Thread.sleep(1000);
      } catch (InterruptedException ex) {
        Thread.currentThread().interrupt(); // very important
        break;
      }

Answer 2

wait() , /, , / . .

, , wait(), () , .

Answer 3

, yield(), - , , -op. (, wait (1000)).

- , -, - , - ..

, . Java concurrency, .