New behavior allows for the ant script to specify a maximum number of
threads that will be executed in parallel. One should be very careful about
using the waitFor
task when specifying threadCount
as it can cause deadlocks if the number of threads is too small or if one of
the nested tasks fails to execute completely. The task selection algorithm
will insure that the tasks listed before a task have started before that
task is started, but it will not insure a successful completion of those
tasks or that those tasks will finish first (i.e. it's a classic race
condition).
Attribute | Description | Type | Required? |
pollinterval | Interval to poll for completed threads when threadCount or threadsPerProcessor is specified. Integer in milliseconds.; optional | int | ? |
threadsperprocessor |
Dynamically generates the number of threads to execute based on the
number of available processors (via
java.lang.Runtime.availableProcessors() ). Requires a J2SE
1.4 VM, and it will overwrite the value set in threadCount.
If used in a 1.1, 1.2, or 1.3 VM then the task will defer to
threadCount .; optional
|
int | ? |
timeout | Sets the timeout on this set of tasks. If the timeout is reached before the other threads complete, the execution of this task completes with an exception. Note that existing threads continue to run. | long | ? |
threadcount |
Statically determine the maximum number of tasks to execute
simultaneously. If there are less tasks than threads then all will be
executed at once, if there are more then only threadCount
tasks will be executed at one time. If threadsPerProcessor
is set and the JVM is at least a 1.4 VM then this value is
ignored.; optional
|
int | ? |
failonany | Control whether a failure in a nested task halts execution. Note that the task will complete but existing threads will continue to run - they are not stopped | boolean | ? |
This Task is a Container (it accepts nested Tasks).
Attribute | Description | Type | Required |