The key facilities that
BlockingQueue provides to such systems are, as its name implies, enqueuing and dequeueing methods that do not return until they have executed successfully. So, for example, a print server does not need to constantly poll the queue to discover whether any print jobs are waiting; it need only call the
poll method, supplying a timeout, and the system will suspend it until either a queue element becomes available or the timeout expires.
BlockingQueue defines seven new methods, in three groups:
Group1 : Adding an Element
boolean offer(E e, long timeout, TimeUnit unit)
// insert e, waiting up to the timeout
void put(E e) // add e, waiting as long as necessary
The nonblocking overload of offer defined in Queue will return false if it cannot immediately insert the element. This new overload waits for a time specified using java.util.concurrent.TimeUnit, an Enum which allows timeouts to be defined in units such as milliseconds or seconds.
Taking these methods together with those inherited from Queue, there are four ways in which the methods for adding elements to a BlockingQueue can behave: offer returns false if it does not succeed immediately, blocking offer returns false if it does not succeed within its timeout, add throws an exception if it does not succeed immediately, and put blocks until it succeeds.
Group2 : Removing an Element
E poll(long timeout, TimeUnit unit)
// retrieve and remove the head, waiting up to the timeout
E take() // retrieve and remove the head of this queue, waiting
// as long as necessary
Again taking these methods together with those inherited from Queue, there are four ways in which the methods for removing elements from a BlockingQueue can behave: poll returns null if it does not succeed immediately, blocking poll returns null if it does not succeed within its timeout, remove throws an exception if it does not succeed immediately, and take blocks until it succeeds.
Group 3 : Retrieving or Querying the Contents of the Queue
int drainTo(Collection<? super E> c)
// clear the queue into c
int drainTo(Collection<? super E> c, int maxElements)
// clear at most the specified number of elements into c
int remainingCapacity()
// return the number of elements that would be accepted
// without blocking, or Integer.MAX_VALUE if unbounded
The drainTo methods perform atomically and efficiently, so the second overload is useful in situations in which you know that you have processing capability available immediately for a certain number of elements, and the first is useful for example when all producer threads have stopped working. Their return value is the number of elements transferred. RemainingCapacity reports the spare capacity of the queue, although as with any such value in multi-threaded contexts, the result of a call should not be used as part of a test-then-act sequence; between the test (the call of remainingCapacity) and the action (adding an element to the queue) of one thread, another thread might have intervened to add or remove elements.
BlockingQueue guarantees that the queue operations of its implementations will be thread-safe and atomic.
But this guarantee doesn't extend to the bulk operations inherited from CollectionaddAll, containsAll, retainAll and removeAllunless the individual implementation provides it. So it is possible, for example, for addAll to fail, throwing an exception, after adding only some of the elements in a collection.
Blocking queue has the following characteristics:
- methods to add an item to the queue, waiting for space to become available in the queue if necessary;
- corresponding methods that take an item from the queue, waiting for an item to put in the queue if it is empty;
- optional time limits and interruptibility on the latter calls;
- efficient thread-safety: blocking queues are specifically designed to have their put() method called from one thread and the take() method from another— in particular, items posted to the queue will be published correctly to any other thread taking the item from the queue again; significantly, the implementations generally achieve this without locking the entire queue, making them highly concurrent components;
- integration with Java thread pools: a flavour of blocking queue can be passed into the constructor of ThreadPoolExecutor to customise the behaviour of the thread pool.
Implementations of blocking queueArrayBlockingQueue : A simple bounded BloickingQueue implementation backed by an array.
DelayQueue : An unbounded blocking queue of Delayed elements, in which an element can only be taken when its delay has expired.It uses elements that implement the new java.util.concurrent.Delayed interface.
PriorityBlockingQueue : This queue bases ordering on a specified Comparator, and the element returned by any take( ) call is the smallest element based on this ordering.
LinkedBlockingQueue : A simple bounded BloickingQueue implementation backed by a linked list.
SynchronousQueue : This queue has a size of zero (yes, you read that correctly). It blocks put( ) calls until another thread calls take( ), and blocks take( ) calls until another thread calls put( ). Essentially, elements can only go directly from a producer to a consumer, and nothing is stored in the queue itself (other than for transition purposes).
Example - Producer consumer problem with Blocking queueThe queue takes care of all the details of synchronizing access to its contents and notifying other threads of the availability of data.
Producer.javapublic class Producer extends Thread {
private BlockingQueue cubbyhole;
private int number;
public Producer(BlockingQueue c, int num) {
cubbyhole = c;
number = num;
}
public void run() {
for (int i = 0; i < 10; i++) {
try {
cubbyhole.put(i);
System.out.format("Producer #%d put: %d%n", number, i);
sleep((int)(Math.random() * 100));
} catch (InterruptedException e) { }
}
}
}
Consumer.javaimport java.util.concurrent.*;
public class Consumer extends Thread {
private BlockingQueue<Integer> cubbyhole;
private int number;
public Consumer(BlockingQueue<Integer> c, int num) {
cubbyhole = c;
number = num;
}
public void run() {
int value = 0;
for (int i = 0; i < 10; i++) {
try {
value = cubbyhole.take();
System.out.format("Consumer #%d got: %d%n", number, value);
} catch (InterruptedException e) { }
}
}
}
ProducerConsumerTest.javapublic class ProducerConsumerTest {
public static void main(String[] args) {
ArrayBlockingQueue c = new ArrayBlockingQueue(1);
Producer p1 = new Producer(c, 1);
Consumer c1 = new Consumer(c, 1);
p1.start();
c1.start();
}
}
Possible Use cases for BlockingQueueThese features make
BlockingQueues useful for cases such as the following:
- a server, where incoming connections are placed on a queue, and a pool of threads picks them up as those threads become free;
- in a variety of parallel processes, where we want to manage or limit resource usage at different stages of the process.
