Bug 5986 - New fault type for job resource expiration
: New fault type for job resource expiration
Status: RESOLVED FIXED
: GRAM
wsrf managed execution job service
: development
: Macintosh All
: P3 normal
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-04-04 16:47 by
Modified: 2008-04-17 15:45 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-04-04 16:47:15
If a job resource lifetime expires, then a failed job notification is sent. 
Currently, a client (like globusrun-ws) does not know from the fault type that
for this failed job, the job resources has already been destroyed.  If a client
tries to destroy the job, they will get a resource not found exception.

With a new "jobResourceExpired" fault type, a client would be able to know that
they should not attempt to terminate the job resource.
------- Comment #1 From 2008-04-08 22:45:24 -------
Added. If a resource expires a failed notification is sent after
cleanup that contains this fault type
------- Comment #2 From 2008-04-17 10:50:10 -------
The type is JobResourceExpiredFaultType and it's an extension of
the existing type FaultType. globusrun-ws is probably capable of
handling it in the fault element of the notification message.

Might be good if globusrun-ws does not explicitly call terminate()
on such a resource
------- Comment #3 From 2008-04-17 15:45:38 -------
Done.