BES clients when getting status of the failed activity, returned response from BESFactory should contain a sub-state describe reason of the failure.
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">
<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>
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.