[FALCON-1325] Triage API on prism, for an instance at which a process does not exist sends incorrect message

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7
• Fix Version/s: 0.7

Environment

QA

• Assignee: Ajay Yadav
• Reporter: Karishma Gulati
• Created: 23/Jul/15 12:44
• Updated: 28/Aug/15 12:16
• Resolved: 28/Aug/15 12:16

Description

For a process which does not have an instance at a particular time, on attempting triage (on prism) at that instance, the following response is received:

<?xml version="1.0" encoding="UTF-8"?><result>
  <status>FAILED</status>
  <message>ua1/org.apache.falcon.FalconException::javax.ws.rs.WebApplicationException: javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"instancesResult"). Expected elements are &lt;{}edge&gt;,&lt;{}result&gt;
</message>
  <requestId>ua1/1702302716@qtp-1143371233-91 - 90918b65-2bc9-4db4-987d-a0c44c7b4aa0
</requestId>
</result>

Sub-Tasks

• Triage Result throws incorrect error message on prism for an invalid process instance: Resolved