| 1 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
| 2 |
<html> |
<html> |
| 3 |
<head> |
<head> |
| 4 |
<title>JSR 166 Snapshot Introduction.</title> |
<title>JSR 166 Introduction.</title> |
| 5 |
</head> |
</head> |
| 6 |
|
|
| 7 |
<body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000"> |
<body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000"> |
| 8 |
<h1>JSR 166 Snapshot Introduction.</h1> |
<h1>JSR 166 Introduction.</h1> |
| 9 |
|
|
| 10 |
by <a href="http://gee.cs.oswego.edu/dl">Doug Lea</a> |
by <a href="http://gee.cs.oswego.edu/dl">Doug Lea</a> |
| 11 |
<p> |
<p> |
| 12 |
|
|
| 13 |
To join a mailing list discussing this JSR, go to: |
This is the updated JSR166 specification. For further information, go |
| 14 |
<A HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A> . |
to: <A |
| 15 |
|
HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> |
| 16 |
<p> |
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A>. |
| 17 |
<em> |
|
| 18 |
Disclaimer - This prototype is experimental code developed as part of |
<p><em>Note: The javadocs here includes some existing java.util |
| 19 |
JSR166 and made available to the developer community for use |
Collection interfaces and classes that are not part of the JSR-166 |
| 20 |
as-is. It is not a supported product. Use it at your own risk. The |
spec, but are included because JSR-166 methods implement or inherit |
| 21 |
specification, language and implementation are subject to change as a |
from their specifications.</em> |
| 22 |
result of your feedback. Because these features have not yet been |
|
| 23 |
approved for addition to the Java language, there is no schedule for |
<p> JSR-166 introduces package <tt>java.util.concurrent</tt> |
| 24 |
their inclusion in a product. |
containing utility classes commonly useful in concurrent |
| 25 |
</em> |
programming. Like package <tt>java.util</tt>, it includes a few small |
| 26 |
|
standardized extensible frameworks, as well as other classes that |
| 27 |
<p> |
provide useful functionality and are otherwise tedious or difficult to |
| 28 |
Package java.util.concurrent contains utility classes that are |
implement. |
| 29 |
commonly useful in concurrent programming. Like package java.util, it |
|
| 30 |
includes a few small standardized extensible frameworks, as well as |
<p>JSR-166 focusses on breadth, providing critical functionality |
| 31 |
some classes that provide useful functionality and are otherwise |
useful across a wide range of concurrent programming styles and |
| 32 |
tedious or difficult to implement. In this JSR, we have been |
applications, ranging from low-level atomic operations, to |
| 33 |
conservative in selecting only those APIs and implementations that are |
customizable locks and synchronization aids, to various concurrent |
| 34 |
useful enough to encourage nearly all concurrent programmers to use |
data structures, to high-level execution agents including thread |
| 35 |
routinely. JSR 166 also includes a few changes and additions in |
pools. This diversity reflects the range of contexts in which |
| 36 |
packages outside of java.util.concurrent: java.lang, to address |
developers of concurrent programs have been found to require or desire |
| 37 |
uncaught exceptions, and java.util to better integrate queues. |
support not previously available in J2SE, which also keeping the |
| 38 |
The API covers: |
resulting package small; providing only functionality that has been |
| 39 |
|
found to be worthwhile to standardize. |
| 40 |
<ul> |
|
| 41 |
<li> Queues |
<p>Descriptions and brief motivations for the main components may be |
| 42 |
<li> Executors |
found in the associated package documentation. JSR-166 also includes |
| 43 |
<li> Locks |
a few changes and additions in packages outside of |
| 44 |
<li> Condition variables |
java.util.concurrent. Here are brief descriptions. |
|
<li> Atomic variables |
|
|
<li> Timing |
|
|
<li> Synchronizers |
|
|
<li> Concurrent Collections |
|
|
<li> Uncaught Exception Handlers |
|
|
</ul> |
|
|
|
|
|
|
|
|
The main rationale for JSR 166 is that threading primitives, such as |
|
|
synchronized blocks, Object.wait and Object.notify, are insufficient |
|
|
for many programming tasks. Currently, developers can use only the |
|
|
concurrency control constructs provided in the Java language |
|
|
itself. These are too low level for some applications, and are |
|
|
incomplete for others. As a result, application programmers are often |
|
|
forced to implement their own concurrency facilities, resulting in |
|
|
enormous duplication of effort creating facilities that are |
|
|
notoriously hard to get right and even harder to optimize. Offering a |
|
|
standard set of concurrency utilities will ease the task of writing a |
|
|
wide variety of multithreaded applications and generally improve the |
|
|
quality of the applications that use them. |
|
|
|
|
|
<p> |
|
|
Here are brief descriptions and rationales of the main components. |
|
|
For details see the javadocs at <a |
|
|
href="http://gee.cs.oswego.edu/dl/concurrent/index.html">http://gee.cs.oswego.edu/dl/concurrent/index.html</a> |
|
|
|
|
| 45 |
|
|
| 46 |
<h2>Queues</h2> |
<h2>Queues</h2> |
| 47 |
|
|
| 48 |
A basic (nonblocking) Queue interface that is compatatible with |
A basic (nonblocking) {@link java.util.Queue} interface extending |
| 49 |
java.util.Collections will be introduced into java.util. Also, |
{@link java.util.Collection} is introduced into |
| 50 |
although it is at the borders of being in scope of JSR-166, |
<tt>java.util</tt>. Existing class {@link java.util.LinkedList} is |
| 51 |
java.util.LinkedList will be adapted to support Queue, and |
adapted to support Queue, and a new non-thread-safe {@link |
| 52 |
a new non-thread-safe java.util.HeapPriorityQueue will be added. |
java.util.PriorityQueue} is added. |
| 53 |
|
|
| 54 |
<p> Five implementations in java.util.concurrent support the extended |
<h2>Threads</h2> |
| 55 |
BlockingQueue interface, that defines blocking versions of put and |
|
| 56 |
take: LinkedBlockingQueue, ArrayBlockingQueue, SynchronousQueue, |
Three minor changes are introduced to the {@link java.lang.Thread} |
| 57 |
PriorityBlockingQueue, and DelayQueue. Additionally, |
class: |
| 58 |
java.util.concurrent.LinkedQueue supplies an efficient thread-safe |
<ul> |
| 59 |
non-blocking queue. |
<li> It now allows per-thread installation of handlers for uncaught |
| 60 |
|
exceptions. Ths optionally disassociates handlers from ThreadGroups, |
| 61 |
<p> Since the target release is JDK1.5, and generics are slated to be |
which has proven to be too inflexible. (Note that the combination of |
| 62 |
in 1.5, Queues are parametrized on element type. (Also some others |
features in JSR-166 make ThreadGroups even less likely to be used in |
| 63 |
below.) |
most programs. Perhaps they will eventually be deprecated.) |
| 64 |
|
|
| 65 |
|
<li> Access checks are no longer required when a Thread interrupts |
| 66 |
<h2>Executors</h2> |
<em>itself</em>. The <tt>interrupt</tt> method is the only way to |
| 67 |
|
re-assert a thread's interruption status (and in the case of |
| 68 |
Executors provide a simple standardized interface for defining custom |
self-interruption has no other effect than this). The check here |
| 69 |
thread-like subsystems, including thread pools, asynch-IO, and |
previously caused unjustifiable and uncontrollable failures when |
| 70 |
lightweight task frameworks. Executors also standardize ways of |
restricted code invoked library code that must reassert interruption |
| 71 |
calling threads that compute functions returning results, via |
to correctly propagate status when encountering some |
| 72 |
Futures. This is supported in part by defining interface Callable, the |
<tt>InterruptedExceptions</tt>. |
| 73 |
argument/result analog of Runnable. |
<li> The <tt>destroy</tt> method, which has never been implemented, |
| 74 |
|
has finally been deprecated. This is just a spec change, reflecting |
| 75 |
<p> While the Executor framework is intended to be extensible the most |
the fact that that the reason it has never been implemented is that |
| 76 |
commonly used Executor will be ThreadExecutor, which can be configured |
it was undesirable and unworkable. |
| 77 |
to act as all sorts of thread pools, background threads, etc. The |
</ul> |
|
class is designed to be general enough to suffice for the vast |
|
|
majority of usages, even sophisticated ones, yet also includes methods |
|
|
and functionality that simplify routine usage. |
|
|
|
|
|
<h2>Locks</h2> |
|
|
|
|
|
The Lock interface supports locking disciplines that differ in |
|
|
semantics (reentrant, semaphore-based, etc), and that can be used in |
|
|
non-block-structured contexts including hand-over-hand and lock |
|
|
reordering algorithms. This flexibility comes at the price of more |
|
|
awkward syntax. Implementations include Semaphore, ReentrantMutex |
|
|
FIFOSemaphore, and CountDownLatch. |
|
|
|
|
|
<p> |
|
|
The Locks class additionally supports trylock-designs using builtin |
|
|
locks without needing to use Lock classes. This requires adding new |
|
|
capabilities to builtin locks inside JVMs. |
|
|
|
|
|
<p> |
|
|
A ReadWriteLock interface similarly defines locks that may be shared |
|
|
among readers but are exclusive to writers. For this release, only a |
|
|
single implementation, ReentrantReadWriteLock, is planned, since it |
|
|
covers all standard usage contexts. But programmers may create their |
|
|
own implementations to cover nonstandard requirements. |
|
|
|
|
|
<h2>Conditions</h2> |
|
|
|
|
|
A Condition class provides the kinds of condition variables associated |
|
|
with monitors in other cocurrent languages, as well as pthreads |
|
|
condvars. Their support reduces the need for tricky and/or |
|
|
inefficient solutions to many classic concurrent problems. Conditions |
|
|
also address the annoying problem that Object.wait(msecs) does not |
|
|
return an indication of whether the wait timed out. This leads to |
|
|
error-prone code. Since this method is in class Object, the problem is |
|
|
basically unfixable. |
|
|
<p> |
|
|
To avoid compatibility problems, the names of Condition methods need |
|
|
to be different than Object versions. The downside of this is that |
|
|
people can make the mistake of calling cond.notify instead of |
|
|
cond.signal. However, they will get IllegalMonitorState exceptions if |
|
|
they do, so they can detect the error if they ever run the code. |
|
|
<p> |
|
|
The implementation requires VM magic to atomically suspend and release |
|
|
lock. But it is unlikely to be very challenging for JVM providers, |
|
|
since most layer Java monitors on top of posix condvars or similar |
|
|
low-level functionality anyway. |
|
|
|
|
|
<h2>Atomic variables</h2> |
|
|
|
|
|
Classes AtomicInteger, AtomicLong, AtomicDouble, AtomicFloat, and |
|
|
AtomicReference provide simple scalar variables supporting |
|
|
compareAndSwap (CAS) and related atomic operations. These are |
|
|
desparately needed by those performing low-level concurrent system |
|
|
programming, but much less commonly useful in higher-level frameworks. |
|
|
|
|
| 78 |
|
|
| 79 |
<h2>Timing</h2> |
<h2>Timing</h2> |
| 80 |
|
|
| 81 |
Java has always supported sub-millisecond versions of several native |
Method <tt>nanoTime</tt> is added to {@link java.lang.System}. It |
| 82 |
time-out-based methods (such as Object.wait), but not methods to |
provides a high-precision timing facility that is distinct from and |
| 83 |
actually perform timing in finer-grained units. We address this by |
uncoordinated with <tt>System.currentTimeMillis</tt>. |
| 84 |
introducing class Clock, which provides multiple granularities for |
|
| 85 |
both accessing time and performing time-out based operations. |
<h2>Removing ThreadLocals</h2> |
| 86 |
|
|
| 87 |
|
The {@link java.lang.ThreadLocal} class now supports a means to remove |
| 88 |
<h2>Synchronizers</h2> |
a ThreadLocal, which is needed in some thread-pool and worker-thread |
| 89 |
|
designs. |
| 90 |
Five classes aid common special-purpose synchronization idioms. |
|
| 91 |
Semaphores and FifoSemaphores are classic concurrency tools. Latches |
|
|
are very simple yet very common objects useful for blocking until a |
|
|
single signal, event, or condition holds. CyclicBarriers are |
|
|
resettable multiway synchronization points very common in some styles |
|
|
of parallel programming. Exchangers allow two threads to exchange |
|
|
objects at a rendezvous point. |
|
|
|
|
|
|
|
|
<h2>Concurrent Collections</h2> |
|
|
|
|
|
JSR 166 will supply a few Collection implementations designed for use |
|
|
in multithreaded contexts: ConcurrentHashTable, CopyOnWriteArrayList, |
|
|
and CopyOnWriteArraySet. |
|
|
|
|
|
<h2>Uncaught Exception Handlers</h2> |
|
|
|
|
|
The java.lang.Thread class will be modified to allow per-thread |
|
|
installation of handlers for uncaught exceptions. Ths optionally |
|
|
disassociates these handlers from ThreadGroups, which has proven to be |
|
|
too inflexible in many multithreaded programs. (Note that the combination |
|
|
of features in JSR 166 make ThreadGroups even less likely to |
|
|
be used in most programs. Perhaps they will eventually be deprecated.) |
|
|
<p> |
|
|
Additionally, ThreadLocals will now support a means to |
|
|
remove a ThreadLocals, which is needed in some thread-pool and |
|
|
worker-thread designs. |
|
| 92 |
|
|
| 93 |
<hr> |
<hr> |
|
<address><A HREF="http://gee.cs.oswego.edu/dl">Doug Lea</A></address> |
|
| 94 |
</body> |
</body> |
| 95 |
</html> |
</html> |
Parent Directory
| 
Revision Log
| 
Patch