Executoris a simple standardized interface for defining custom thread-like subsystems, including thread pools, asynchronous I/O, and lightweight task frameworks. Depending on which concrete Executor class is being used, tasks may execute in a newly created thread, an existing task-execution thread, or the thread calling
execute, and may execute sequentially or concurrently.
ExecutorServiceprovides a more complete asynchronous task execution framework. An ExecutorService manages queuing and scheduling of tasks, and allows controlled shutdown. The
ScheduledExecutorServicesubinterface and associated interfaces add support for delayed and periodic task execution. ExecutorServices provide methods arranging asynchronous execution of any function expressed as
Callable, the result-bearing analog of
Futurereturns the results of a function, allows determination of whether execution has completed, and provides a means to cancel execution. A
Futurethat possesses a
runmethod that upon execution, sets its results.
provide tunable, flexible thread pools.
Executors class provides
factory methods for the most common kinds and configurations
of Executors, as well as a few utility methods for using
them. Other utilities based on
Executors include the
providing a common extensible implementation of Futures, and
assists in coordinating the processing of groups of
ForkJoinPool provides an
Executor primarily designed for processing instances of
ForkJoinTask and its subclasses. These
classes employ a work-stealing scheduler that attains high
throughput for tasks conforming to restrictions that often hold in
computation-intensive parallel processing.
ConcurrentLinkedQueueclass supplies an efficient scalable thread-safe non-blocking FIFO queue. The
ConcurrentLinkedDequeclass is similar, but additionally supports the
Five implementations in
interface, that defines blocking versions of put and take:
The different classes cover the most common usage contexts
for producer-consumer, messaging, parallel tasking, and
related concurrent designs.
introduce a synchronous
transfer method (along with related
features) in which a producer may optionally block awaiting its
TimeUnitclass provides multiple granularities (including nanoseconds) for specifying and controlling time-out based operations. Most classes in the package contain operations based on time-outs in addition to indefinite waits. In all cases that time-outs are used, the time-out specifies the minimum time that the method should wait before indicating that it timed-out. Implementations make a "best effort" to detect time-outs as soon as possible after they occur. However, an indefinite amount of time may elapse between a time-out being detected and a thread actually executing again after that time-out. All methods that accept timeout parameters treat values less than or equal to zero to mean not to wait at all. To wait "forever", you can use a value of
SynchronizersFive classes aid common special-purpose synchronization idioms.
Semaphoreis a classic concurrency tool.
CountDownLatchis a very simple yet very common utility for blocking until a given number of signals, events, or conditions hold.
CyclicBarrieris a resettable multiway synchronization point useful in some styles of parallel programming.
Phaserprovides a more flexible form of barrier that may be used to control phased computation among multiple threads.
Exchangerallows two threads to exchange objects at a rendezvous point, and is useful in several pipeline designs.
Concurrent CollectionsBesides Queues, this package supplies Collection implementations designed for use in multithreaded contexts:
CopyOnWriteArraySet. When many threads are expected to access a given collection, a
ConcurrentHashMapis normally preferable to a synchronized
HashMap, and a
ConcurrentSkipListMapis normally preferable to a synchronized
CopyOnWriteArrayListis preferable to a synchronized
ArrayListwhen the expected number of reads and traversals greatly outnumber the number of updates to a list.
The "Concurrent" prefix used with some classes in this package
is a shorthand indicating several differences from similar
"synchronized" classes. For example
Collections.synchronizedMap(new HashMap()) are
ConcurrentHashMap is "concurrent". A
concurrent collection is thread-safe, but not governed by a
single exclusion lock. In the particular case of
ConcurrentHashMap, it safely permits any number of
concurrent reads as well as a large number of concurrent
writes. "Synchronized" classes can be useful when you need
to prevent all access to a collection via a single lock, at
the expense of poorer scalability. In other cases in which
multiple threads are expected to access a common collection,
"concurrent" versions are normally preferable. And
unsynchronized collections are preferable when either
collections are unshared, or are accessible only when
holding other locks.
Most concurrent Collection implementations
(including most Queues) also differ from the usual
conventions in that their Iterators
and Spliterators provide
weakly consistent rather than fast-fail traversal:
- they may proceed concurrently with other operations
- they will never throw
- they are guaranteed to traverse elements as they existed upon construction exactly once, and may (but are not guaranteed to) reflect any modifications subsequent to construction.
Memory Consistency PropertiesChapter 17 of The Java Language Specification defines the happens-before relation on memory operations such as reads and writes of shared variables. The results of a write by one thread are guaranteed to be visible to a read by another thread only if the write operation happens-before the read operation. The
volatileconstructs, as well as the
Thread.join()methods, can form happens-before relationships. In particular:
- Each action in a thread happens-before every action in that thread that comes later in the program's order.
- An unlock (
synchronizedblock or method exit) of a monitor happens-before every subsequent lock (
synchronizedblock or method entry) of that same monitor. And because the happens-before relation is transitive, all actions of a thread prior to unlocking happen-before all actions subsequent to any thread locking that monitor.
- A write to a
volatilefield happens-before every subsequent read of that same field. Writes and reads of
volatilefields have similar memory consistency effects as entering and exiting monitors, but do not entail mutual exclusion locking.
- A call to
starton a thread happens-before any action in the started thread.
- All actions in a thread happen-before any other thread
successfully returns from a
joinon that thread.
java.util.concurrentand its subpackages extend these guarantees to higher-level synchronization. In particular:
- Actions in a thread prior to placing an object into any concurrent collection happen-before actions subsequent to the access or removal of that element from the collection in another thread.
- Actions in a thread prior to the submission of a
Executorhappen-before its execution begins. Similarly for
Callablessubmitted to an
- Actions taken by the asynchronous computation represented by a
Futurehappen-before actions subsequent to the retrieval of the result via
Future.get()in another thread.
- Actions prior to "releasing" synchronizer methods such as
CountDownLatch.countDownhappen-before actions subsequent to a successful "acquiring" method such as
CountDownLatch.awaiton the same synchronizer object in another thread.
- For each pair of threads that successfully exchange objects via
Exchanger, actions prior to the
exchange()in each thread happen-before those subsequent to the corresponding
exchange()in another thread.
- Actions prior to calling
Phaser.awaitAdvance(as well as its variants) happen-before actions performed by the barrier action, and actions performed by the barrier action happen-before actions subsequent to a successful return from the corresponding
awaitin other threads.
- See Java Language Specification:
17.4.5 Happens-before Order
ClassDescriptionProvides default implementations of
ExecutorServiceexecution methods.A bounded blocking queue backed by an array.A
Dequethat additionally supports blocking operations that wait for the deque to become non-empty when retrieving an element, and wait for space to become available in the deque when storing an element.A
Queuethat additionally supports operations that wait for the queue to become non-empty when retrieving an element, and wait for space to become available in the queue when storing an element.Exception thrown when a thread tries to wait upon a barrier that is in a broken state, or which enters the broken state while the thread is waiting.Callable<V>A task that returns a result and may throw an exception.Exception indicating that the result of a value-producing task, such as a
FutureTask, cannot be retrieved because the task was cancelled.A marker interface identifying asynchronous tasks produced by
asyncmethods.Exception thrown when an error or other exception is encountered in the course of completing a result or task.A service that decouples the production of new asynchronous tasks from the consumption of the results of completed tasks.A stage of a possibly asynchronous computation, that performs an action or computes a value when another CompletionStage completes.ConcurrentHashMap<K,
V>A hash table supporting full concurrency of retrievals and high expected concurrency for updates.A view of a ConcurrentHashMap as a
Setof keys, in which additions may optionally be enabled by mapping to a common value.An unbounded concurrent deque based on linked nodes.An unbounded thread-safe queue based on linked nodes.ConcurrentMap<K,
Mapproviding thread safety and atomicity guarantees.A scalable concurrent
ConcurrentNavigableMapimplementation.A thread-safe variant of
ArrayListin which all mutative operations (
set, and so on) are implemented by making a fresh copy of the underlying array.A synchronization aid that allows one or more threads to wait until a set of operations being performed in other threads completes.A
ForkJoinTaskwith a completion action performed when triggered and there are no remaining pending actions.A synchronization aid that allows a set of threads to all wait for each other to reach a common barrier point.A mix-in style interface for marking objects that should be acted upon after a given delay.An unbounded blocking queue of
Delayedelements, in which an element can only be taken when its delay has expired.Exchanger<V>A synchronization point at which threads can pair and swap elements within pairs.Exception thrown when attempting to retrieve the result of a task that aborted by throwing an exception.An object that executes submitted
R>A component that acts as both a Subscriber and Publisher.A producer of items (and related control messages) received by Subscribers.A receiver of messages.Factory for creating new
ForkJoinWorkerThreads.Interface for extending managed parallelism for tasks running in
ForkJoinPools.ForkJoinTask<V>Abstract base class for tasks that run within a
Futurerepresents the result of an asynchronous computation.Represents the computation state.FutureTask<V>A cancellable asynchronous computation.An optionally-bounded blocking deque based on linked nodes.An optionally-bounded blocking queue based on linked nodes.An unbounded
TransferQueuebased on linked nodes.A recursive resultless
ForkJoinTask.A recursive result-bearing
ForkJoinTask.Exception thrown by an
Executorwhen a task cannot be accepted for execution.A handler for tasks that cannot be executed by a
ExecutorServicethat can schedule commands to run after a given delay, or to execute periodically.A delayed result-bearing action that can be cancelled.A
ThreadPoolExecutorthat can additionally schedule commands to run after a given delay, or to execute periodically.A counting semaphore.A
Flow.Publisherthat asynchronously issues submitted (non-null) items to current subscribers until it is closed.A blocking queue in which each insert operation must wait for a corresponding remove operation by another thread, and vice versa.An object that creates new threads on demand.A random number generator (with period 264) isolated to the current thread.A handler for rejected tasks that throws a
RejectedExecutionException.A handler for rejected tasks that runs the rejected task directly in the calling thread of the
executemethod, unless the executor has been shut down, in which case the task is discarded.A handler for rejected tasks that discards the oldest unhandled request and then retries
execute, unless the executor is shut down, in which case the task is discarded.A handler for rejected tasks that silently discards the rejected task.Exception thrown when a blocking operation times out.A
TimeUnitrepresents time durations at a given unit of granularity and provides utility methods to convert across units, and to perform timing and delay operations in these units.A
BlockingQueuein which producers may wait for consumers to receive elements.