Exception on basis of Acknowledgement

[Former Member]

Hi All,

My scenario is as follows:-

BPM tries to send message asynchronously to a file Interface through a send step.

The send step receives an acknowledgement by setting up the Acknowledgement Mode=Transport . The BPM need to trigger an exception, if the adapter is not able to deliver the message to the File Server for any reason.( i.e.for an negetive acknowledgement)

I am following the blog by Micahel [http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3875] [original link is broken];

I am trying to simulate a messaging failure by putting wrong value in my communication channel.I have set the value for the Deadline Step as 1 min(which is the minimum I can put). But the exception is not getting triggered. I am getting the following error within 1 min.

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

For the correct value in the communication channel, I am getting the desired result.

I tried to set the value for CHECK_FOR_ASYNC_RESPONSE_TIMEOUT parameter under category SA_COMM (TCODE SXMB_ADMIN) to 120 seconds, but still I am encountering the same error.

Can you please suggest the corrective measure?

Regards,

SS

[Former Member]

Solved it myself.so closing the thread

[maciej_jarecki]

Hi

It seems that your CC has default setting and Adpater engine will process message 3 times with time interval 5 minutes. Change those settings using this blog

or in your NWA.

Regards

Maciej