#247 U.BES:Extend FAILED state with substates describe cause

UNICORE 6.4
closed
UNICORE/X (47)
5
2011-10-05
2011-08-09
No

BES clients when getting status of the failed activity, returned response from BESFactory should contain a sub-state describe reason of the failure.

Discussion

  • Shahbaz Memon

    Shahbaz Memon - 2011-10-05
    • status: open --> closed
     
  • Shahbaz Memon

    Shahbaz Memon - 2011-10-05

    BESFactory returns a Failed state with appropriate soap fault, see example below,

    <xml-fragment state="Failed" xmlns:bes="http://schemas.ggf.org/bes/2006/08/bes-factory" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <bes:ExitCode>0</bes:ExitCode>
    <soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:faultcode>bes:UnknownActivityExecutionFault</soapenv:faultcode>
    <soapenv:faultstring>Stage in was NOT SUCCESSFUL: Filetransfer FAILED: /bin/sleep -> /bin/test.dat, error message: File transfer failed: java.io.FileNotFoundException: /tmp/bes/FILESPACE/6fa15b17-a33f-4ee5-9215-de9cea3aa1ef/bin/test.dat (No such file or directory)</soapenv:faultstring>
    </soapenv:Fault>
    </xml-fragment>

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks