In my problematic business process, a synchronous sending step is used to send a request to a web service and get the response of the web service. A following transformation step converts the received response message to another message. Error occurs in this process.
If I doesn't use the response as the input of the transformation, no error occurs.
It seems that there's some problem in the response message. But that message can be correctly sent in a send step (close S/A mode).
The error message is like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
- http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack>
Does anybody have similar experience?