BPM Sync/Async Scenario: error: "Timeout condition of pipeline reached"..!

[Former Member]

Hi,

I am doing Sync/Async BPM scenario.

-> Receive message and process and response back to the sender.

Sometimes it will correct correctly. Sometime the message will come and stay in XI and fails with error

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

I observed that the messages will stay in transaction "SXMS_SAMON" . and will fail after sometime.

What might be the reason. ? what need to do to stop these kind of errors?

Thanks

Deepthi.

[Former Member]

Guys,

Can you believe it..!!

Someone created the entry in SMQS for Destination "WORKFLOW_LOCAL_100" and made it as Unregistered. That's the reason the messages are not executing in SMQ1 and SM58 which are used by RFC "WORKFLOW_LOCAL_100".

Thank you for your help.

[former_member181985]

What is your scenario flow?

[Former Member]

Hi Praveen,

Webservice <--> XI -->BW .

BPM :

start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoBW)->Send(Send Response) ---> stop.

Messages are getting struck in SMQ1 and SM58 at these three points.

1. Message comes and stays in SXMB_MONI in status "Log Version"

The messages are stuck in SMQ1 in READY status without doing any processing.

XBQO$PE_WS90100002 WORKFLOW_LOCAL_100 1 READY 26.02.2009

Once I push the queue by Activating/Unlocking, it will process.

2. when it is trying to send the message to R/3 (Backend system) it is waiting in SM58 with below entry.

WF-BATCH SWW_WI_EXECUTE_INTERNAL_RFC WORKFLOW_LOCAL_100 Transaction recorded

Manually I execute LUW to push it. Once I done the message will go to R/3 system and Response mapping also complete.

3. Again it is waiting at SM58 with below deatails while sending the response to sender.

PIAFUSER SWW_WI_COMP_EVENT_RECEIVE_IBF WORKFLOW_LOCAL_100 Transaction recorded

we are again manually execute LUW. Once we done the response message will go back to Sender.

Any Idea to solve this..?

Thanks

Deepthi

[Former Member]

it seems to be a connection problem with target system

[Former Member]

I observed that the message is stopping at some queues. Once I activate the queue, it is again taking long time in tRFC in SM58.

This is what happening...

- Message comes and stays in SXMB_MONI in status "Log Version"

- Message will go to Process engine and waits over there in queue XBPE* . This I have checked in transaction "SXMS_SAMON" and I cliked on the message ID which will take me to the queue and I activate the queue here otherwise it is failing with "Timeout reached in pipeline"

- After that it is Waiting for event 'RECEIVED' of object type 'ZXI_PROXY_AA_SALES_REQ_0001'.

- I checked SM58, the tRFC is waiting to execute for a long time. It is taking long time to process here.If I push by executing it is clearing. Otherwise it is staying like that for a long time.

This is happening most of the time. Sometimes few messages will process with any interuption.

Any idea what can be done to stop these ?

[Former Member]

if all your messages are stucked in queue check your dbstatistic

if only this scenario gives problem - there might be some issues with BPM (which version of PI (SP) you are working on.

[Former Member]

>> if all your messages are stucked in queue check your dbstatistic

Can you please elaborate a bit how to do this. I am facing for all the Syncchronous calls which uses BPM. All the Asynchrnous messages working correctly.

We are on PI7.0 SP15 .

[Former Member]

Hi,

Two steps I am doing everytime to push these messages.

1. goto tcode: SXMS_SAMON , click on the message id and it will take you to below queue.

XBQO$PE_WS90100002 WORKFLOW_LOCAL_100 1 READY 26.02.2009

and you need to activate/Unlock it to process further.

2. Goto SM58 and execute below 2 LUW's.

WF-BATCH SWW_WI_EXECUTE_INTERNAL_RFC WORKFLOW_LOCAL_100 Transaction recorded

PIAFUSER SWW_WI_COMP_EVENT_RECEIVE_IBF WORKFLOW_LOCAL_100Transaction recorded

Still I dunno the reason why they are strucked over there.?

Is there anything to do with RFC "WORKFLOW_LOCAL_100" ? I checked in SM59 and the connection is good.

Any one suggest me how to solve this please.

Thanks

Deepthi.

[Former Member]

Hi

check if this note is useful

1124049

Regards

Vishnu