Bug 6134 - GT4.2 RC2: error reporting in globusrun-ws
: GT4.2 RC2: error reporting in globusrun-ws
Status: RESOLVED FIXED
: GRAM
wsrf gram clients
: alpha
: Macintosh All
: P3 critical
: 4.2
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2008-06-06 12:43 by
Modified: 2008-06-09 12:18 (History)


Attachments


Note

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


Description From 2008-06-06 12:43:09
globusrun-ws does not print all the nice explanations when e.g. a job
with staging fails due to an error in staging, but it did so in 4.0.x.

Gram4 in trunk puts all the fault information into the notification
message, as it did in 4.0.x. But due to changes in fault handling,
the fault causes are all nested, not arranged in an array.
(See "Faults" in
http://dev.globus.org/wiki/Java_WS_Core/Final_WSRF_Migration_Guide)

It looks like globusrun-ws grabs the description of the top-level fault
and ignores the descriptions in the nested FaultCauses.

I'll mark it critical, maybe it's a blocker.

I'll add links where to find examples, because attachments are disabled.
------- Comment #2 From 2008-06-09 10:01:13 -------
Seems like we finally agreed, that globusrun-ws just has to look at the
description of a fault, and not dive into the fault causes to get more
information.
In case of an RFT error, Gram on the server-side will pull RFT's fault
description and add it to the fault description of the fault of the job.
------- Comment #3 From 2008-06-09 12:18:05 -------
committed, will be in 4.2.0