PL_TIMEOUT in Sync Async scenario using BPM

[sam_venkat]

Hello:

We sporadically get PL_TIMEOUT error in a S/A scenario. Every time the error occurs when it is trying to close the Synch Asynch bridge in the BPM. The BPM is extremely simple but it often runs for a long time (5-8 minutes) esp in the close S/A bridge step. The timeout parameters are set as follows

TIMEOUT=60 sec

PROCTIMEOUT=900 sec

CHECK_FOR_ASYNC_RESPONSE_TIMEOUT=500 sec (increased this from the default 60 sec recently)

Would increasing TIMEOUT or CHECK_FOR_ASYNC_RESPONSE_TIMEOUT parameters help?

- <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>

[Former Member]

Hi venkat,

These Threads will help you.

Reward points if usefull...

[sam_venkat]

Will try the timeout changes and let you know. Thanks for your inputs.

[Former Member]

Increase the HTTP time out in SXMB_ADM setting

[Shabarish_Nair]

if as u mentioned the BPM is a simple design, then why dont you try and replace the BPM ?

From XI 3.0 SP19 and above you can avoid BPMs for a SYNC-ASYNC scenario - /people/henrique.pinto/blog/2007/08/02/syncasync-scenarios-without-bpm

[Former Member]

Hey

yeah increasing the TIMEOUT will help you but its not recommended to increase it to a very high value,infact you should try to see as to why its taking you time to get response so late and try to reduce that,in case ur unable to reduce that then u can increase the TIMEOUT

Thanx

Aamir