|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
SessionAlreadyActiveException
without detail message.
SessionAlreadyActiveException
with
the specified detail message.
AuthorizationException
without
detail message.
AuthorizationException
with the
specified detail message.
ConflictingAttributeValuesException
without detail message.
ConflictingAttributeValuesException
with the specified detail message.
DefaultContactStringException
without detail message.
DefaultContactStringException
with
the specified detail message.
DeniedByDrmException
without
detail message.
DeniedByDrmException
with the
specified detail message.
CommunicationException
without
detail message.
CommunicationException
with the
specified detail message.
DrmaaException
without detail
message.
DrmaaException
with the specified
detail message.
DrmsExitException
without detail
message.
DrmsExitException
with the specified detail message.
DrmsInitException
without detail
message.
DrmsInitException
with the
specified detail message.
ExitTimeoutException
without
detail message.
ExitTimeoutException
with the
specified detail message.
true
, this method returns a
representation of the signal that caused the termination of the job.
HoldInconsistentStateException
without detail message.
HoldInconsistentStateException
with the specified detail message.
true
, this function returns
true
if a core image of the terminated job was created.
true
if the job terminated normally.
true
if the job terminated due to the receipt
of a signal.
InconsistentStateException
without detail message.
InconsistentStateException
with
the specified detail message.
InternalException
without detail
message.
InternalException
with the
specified detail message.
InvalidAttributeFormatException
without detail message.
InvalidAttributeFormatException
with the specified detail message.
InvalidAttributeValueException
without detail message.
InvalidAttributeValueException
with the specified detail message.
InvalidContextStringException
without detail message.
InvalidContextStringException
with the specified detail message.
InvalidJobException
without detail
message.
InvalidJobException
with the
specified detail message.
InvalidJobException
without detail
message.
InvalidJobException
with the
specified detail message.
NoActiveSessionException
without
detail message.
NoActiveSessionException
with the
specified detail message.
DefaultContactStringException
without detail message.
DefaultContactStringException
with
the specified detail message.
ReleaseInconsistentStateException
without detail message.
ReleaseInconsistentStateException
with the specified detail message.
ResumeInconsistentStateException
without detail message.
ResumeInconsistentStateException
with the specified detail message.
SuspendInconsistentStateException
without detail message.
SuspendInconsistentStateException
with the specified detail message.
JOB_IDS_SESSION_ALL
,
then this method waits for all jobs submitted during this DRMAA
session up to the moment synchronize() is called. To avoid thread race
conditions in multithreaded applications, the DRMAA implementation user
should explicitly synchronize this call with any other job submission
or control calls that may change the number of remote jobs.
To prevent blocking indefinitely in this call, the caller may use a
timeout specifying how many seconds to block in this call. The value
TIMEOUT_WAIT_FOREVER
may be specified to wait indefinitely
for a result. The value TIMEOUT_NO_WAIT
may be specified to
return immediately if no result is available. If the call exits before
the timeout has elapsed, all the jobs have been waited on or there was an
interrupt. If the invocation exits on timeout, an ExitTimeException is
thrown. The caller should check system time before and after this call
in order to be sure of how much time has passed.
The dispose parameter specifies how to treat the reaping of the
remote jobs' internal data records, which includes a record of the jobs'
consumption of system resources during their execution and other
statistical information. If this parameter is set to true
,
the DRM will dispose of the jobs' data records at the end of
the synchroniize() call. If set to false
, the data records
will be left for future access via the wait() method.
TryLaterException
without detail
message.
TryLaterException
with the
specified detail message.
UnsupportedAttributeException
without detail message.
UnsupportedAttributeException
with
the specified detail message.
JOB_IDS_SESSION_ANY
, is
provided as the jobId, this routine will wait for any job from the
session. This routine is modeled on the wait3 POSIX routine.
The timeout value is used to specify the desired behavior when
a result is not immediately available. The value,
TIMEOUT_WAIT_FOREVER
, may be specified to wait indefinitely
for a result. The value,
TIMEOUT_NO_WAIT
, may be specified
to return immediately if no result is available. Alternatively, a number
of seconds may be specified to indicate how long to wait for a result to
become available.
If the call exits before timeout, either the job has been waited on successfully or there was an interrupt. If the invocation exits on timeout, an ExitTimeoutException is thrown. The caller should check system time before and after this call in order to be sure how much time has passed.
The routine reaps job data records on a successful call, so any subsequent calls to wait(), synchronize(), control(), or getJobProgramStatus() will fail, throwing an InvalidJobException, meaning that the job's data record has been already reaped. This exception is the same as if the job were unknown. (The only case where wait() can be successfully called on a single job more than once is when the previous call to wait() timed out before the job finished.)
When successful, the resource usage information for the job is
provided as a Map of usage parameter names and their values in the
JobInfo object. The values contain the amount of resources consumed by
the job and are implementation defined. If no resource usage
information is available for the finished job, the resourceUsage
property of the returned JobInfo instance will be null
.
In the 0.5 version of this method, a NoResourceUsageException would be thrown if the target job finished with no resource usage information. In the current implementation, no exception is thrown in that case. Instead, the JobInfo.getResourceUsage() method will return null.
true
if the job ended before entering the running
state.
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |