@@ -31,10 +31,20 @@ task within the parallel task will be executed in its own thread. </p>
</tr>
<tr>
<td valign="top">pollInterval</td>
<td valign="top">Maximum number of milliseconds to wait for before checking
when waiting for available threads.</td>
<td valign="top">Currently has no effect</td>
<td align="center" valign="top">No, default is 1000</td>
</tr>
<tr>
<td valign="top">timeout</td>
<td valign="top">Number of milliseconds before execution is terminated</td>
<td align="center" valign="top">No</td>
</tr>
<tr>
<td valign="top">failonany</td>
<td valign="top">If any of the nested tasks fails, execution of the task completes
at that point without waiting for any other tasks to complete.</td>
<td align="center" valign="top">No</td>
</tr>
</table>
<p>Parallel tasks have a number of uses in an Ant build file including:</p>
@@ -45,22 +55,25 @@ harness is run in another thread.</li>
</ul>
<p>Care must be taken when using multithreading to ensure the tasks within the
threads do not interact. For example, two javac compile tasks which write
threads do not interact. For example, two javac compile tasks which write
classes into the same destination directory may interact where one tries to
read a class for dependency information while the other task is writing the
class file. Be sure to avoid these types of interactions within a
read a class for dependency information while the other task is writing the
class file. Be sure to avoid these types of interactions within a
<parallel> task</p>
<p>The parallel task has no attributes and does not support any nested
elements apart from Ant tasks. Any valid Ant task may be embedded within a
<p>Any valid Ant task may be embedded within a
parallel task, including other parallel tasks.</p>
<p>Note that while the tasks within the parallel task are being run, the main
thread will be blocked waiting for all the child threads to complete.</p>
<p>Note that while the tasks within the parallel task are being run, the main
thread will be blocked waiting for all the child threads to complete. If
execution is terminated by a timeout or a nested task failure when the failonany
flag is set, the parallel task will complete without waiting for other nested
tasks to complete in other threads.
</p>
<p>If any of the tasks within the <parallel> task fails, the remaining
tasks in other threads will continue to run until all threads have completed.
In this situation, the parallel task will also fail.</p>
<p>If any of the tasks within the <parallel> task fails and failonany is
not set, the remaining tasks in other threads will continue to run until
all threads have completed. In this situation, the parallel task will also fail.</p>
<p>The parallel task may be combined with the <a href="sequential.html">
sequential</a> task to define sequences of tasks to be executed on each thread
@@ -70,7 +83,7 @@ within the parallel block</p>
threads for the execution. When not present all child tasks will be executed at
once. When present then the maximum number of concurrently executing tasks will
not exceed the number of threads specified. Furthermore, each task will be
started in the order they are given. But no guarantee is made as to the speed
started in the order they are given. But no guarantee is made as to the speed
of execution or the order of completion of the tasks, only that each will be
started before the next.<p>
@@ -80,11 +93,11 @@ processors (there is no affinity to a particular processor however). This will
override the value in threadCount. If threadsPerProcessor is specified using
any version prior to 1.4 then the value in threadCount will be used as is.</p>
<p>When using threadCount and threadsPerProcessor care should be taken to i nsure
<p>When using threadCount and threadsPerProcessor care should be taken to e nsure
that the build does not deadlock. This can be caused by tasks such as waitFor
take ing up all available threads before the tasks that would unlock the waitfor
taking up all available threads before the tasks that would unlock the waitfor
would occur. This is not a repalcement for Java Language level thread
semantics and is best used for "embarasingly parallel" tasks.</p>
semantics and is best used for "embarass ingly parallel" tasks.</p>
<h3>Examples</h3>
<pre>
@@ -97,14 +110,14 @@ semantics and is best used for "embarasingly parallel" tasks.</p>
</sequential>
</parallel>
</pre>
<p>This example represents a typical pattern for testing a server application.
In one thread the server is started (the wlrun task). The other thread consists
of a three tasks which are performed in sequence. The sleep task is used to
give the server time to come up. Another task which is capable of validating
that the server is available could be used in place of the sleep task. The
test harness is then run. Once the tests are complete, the server is stopped
(using wlstop in this example), allowing both threads to complete. The
parallel task will also complete at this time and the build will then
<p>This example represents a typical pattern for testing a server application.
In one thread the server is started (the wlrun task). The other thread consists
of a three tasks which are performed in sequence. The sleep task is used to
give the server time to come up. Another task which is capable of validating
that the server is available could be used in place of the sleep task. The
test harness is then run. Once the tests are complete, the server is stopped
(using wlstop in this example), allowing both threads to complete. The
parallel task will also complete at this time and the build will then
continue.</p>
<pre>
@@ -114,10 +127,10 @@ continue.</p>
</parallel>
</pre>
<p>This example shows two independent tasks being run to achieve better
<p>This example shows two independent tasks being run to achieve better
resource utilization during the build. In this instance, some servlets are being
compiled in one thead and a set of JSPs is being precompiled in another. As
noted above, you need to be careful that the two tasks are independent, both in
compiled in one thead and a set of JSPs is being precompiled in another. As
noted above, you need to be careful that the two tasks are independent, both in
terms of their dependencies and in terms of their potential interactions in
Ant's external environment.</p>
@@ -136,7 +149,7 @@ Ant's external environment.</p>
</parallel>
</pre>
<p>This example represents a typical need for use of the threadCount and
<p>This example represents a typical need for use of the threadCount and
threadsPerProcessor attributes. Spinning up all 40 of those tasks could cripple
the JVM for memory and the CPU for available time. By limiting the number of
concurrent executions you can get the task done in about the same assuming