Bug 6036 - bad ResourceUnknown error from globusrun-ws
: bad ResourceUnknown error from globusrun-ws
Status: RESOLVED FIXED
: GRAM
wsrf gram clients
: 4.0.7
: Macintosh All
: P3 normal
: 4.0.8
Assigned To:
:
:
:
: 6192
  Show dependency treegraph
 
Reported: 2008-04-22 14:16 by
Modified: 2008-07-18 14:35 (History)


Attachments


Note

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


Description From 2008-04-22 14:16:34
Sometimes when confronted with an unknown resource, globusrun-ws responds with:
globusrun-ws: Error querying job state
globus_soap_message_module: SOAP Fault
Fault code: soapenv:Server.generalException

When run with -dbg, I don't even see the response from the container:
globusrun-ws -self -dbg  -status -j fake.epr 

=== REQUEST MESSAGE (length 816) (time 1208888966.209291000) ===
<ns00:Envelope
xmlns:ns00="http://schemas.xmlsoap.org/soap/envelope/"><ns00:Header></ns00:Header><ns00:Body><ns01:GetMultipleResourceProperties
xmlns:ns01="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-ResourceProperties-1.2-draft-01.xsd"><ns01:ResourceProperty
xmlns:ns02="http://www.globus.org/namespaces/2004/10/gram/job/types">ns02:state</ns01:ResourceProperty><ns01:ResourceProperty
xmlns:ns02="http://www.globus.org/namespaces/2004/10/gram/job/types">ns02:holding</ns01:ResourceProperty><ns01:ResourceProperty
xmlns:ns03="http://www.globus.org/namespaces/2004/10/gram/job/faults">ns03:fault</ns01:ResourceProperty><ns01:ResourceProperty
xmlns:ns02="http://www.globus.org/namespaces/2004/10/gram/job/types">ns02:exitCode</ns01:ResourceProperty></ns01:GetMultipleResourceProperties></ns00:Body></ns00:Envelope>
----------------------------------------------
globusrun-ws: Error querying job state
globus_soap_message_module: SOAP Fault
Fault code: soapenv:Server.generalException
------- Comment #1 From 2008-04-22 14:18:36 -------
Oh, right - this comes from the OSG user community.  It happens to a user when
he doesn't set the termination time and comes back over 24 hours later to check
on job status.  I've made a note that they should increase their termination
time with -term if they want the status to be available longer, but this
certainly didn't help us debug what was going on.  I would advocate that the
resource unknown error come with an additional explanation that the resource
might have expired.
------- Comment #2 From 2008-04-22 14:44:14 -------
Expired is just one of the possibilities, maybe the error should include all of
this:

The job (resource) attempting to be contacted is not there.  Some possible
reasons are:
  1) It's lifetime expired so it was destroyed by the service
  2) It was already destroyed by user request
  3) The job EPR is erroneous
------- Comment #3 From 2008-04-24 11:03:18 -------
% globusrun-ws -monitor -job-epr-file ~/epr

Old messages:
    globusrun-ws: Error subscribing
    globus_soap_message_module: SOAP Fault
    Fault code: soapenv:Server.generalException
New messages:
    globusrun-ws: Error: invalid or unknown job reference. Job resource may
have expired or been terminated. Unable to subscribe for notifications.

% globusrun-ws -kill -job-epr-file ~/epr   

Old messages:
    Requesting original job description...Failed.    globusrun-ws: Unable to
destroy job: Error querying job submission    globus_soap_message_module: SOAP
Fault
    Fault code: soapenv:Server.generalException

New messages:
    Requesting original job description...Failed.
    globusrun-ws: Unable to destroy job: Error: invalid or unknown job
reference
. Job resource may have expired or been terminated. Unable to query job
descript
ion document.

% globusrun-ws -status -job-epr-file ~/epr
Old messages:
    globusrun-ws: Error querying job state
    globus_soap_message_module: SOAP Fault
    Fault code: soapenv:Server.generalException

New messages:
    globusrun-ws: Error: invalid or unknown job resource while querying job
stat
e. Job may have expired or been destroyed.