PL_TIMEOUT in BPM
Hi
I have a BPM with a fork with 2 branches. It receives a sync request, post an async idoc and return response.
Branch 1 - post Idoc, wait for transport acknowledgement and then map OK message back to sender
Branch 2 - wait step (1 minute), map to timeout-error and send response.
If Idoc posts ok, the OK-mapping will be returned to sender. If Idoc wait more than 60 seconds for an acknowledgement, the PL_TIMEOUT error kicks in. I have set the parameter SA_COMM - CHECK_FOR_ASYNCH_RESPONSE to 75 seconds to be able to run the BPM process after the WAIT step has finished. Still, the PL_TIMEOUT kicks in and the error-response is not sent back.
Anyone have any idea what it may be? DId I explain myself good enough?
Thanks!
regards Marianne
Hi Marianne,
i think you need to define a exception in idoc send step and a exception branch catching that error for branch 1, where you put the same error handling as in branch 2.
Regards,
Udo
Similar Messages
-
Help on PL_TIMEOUT error in BPM
Hi
I am trying a BPM scenario (SOAP-RFC Synchronous communication), where I have to call a sequence of BAPI's. I am laying out the whole scenario over here.
Sender: Web Service
Receiver: SAP R/3 System
I have a webservice which acts as a sender system and I have to call two BAPI's for which I am using BPM. Here I have to get the result from the 2nd BAPI and send the result as a response back to the Webservice.
I have designed the BPM like below:
1. Receiver Step:
mode: Sync/Async Bridge open
msg: webservice request
Synchronous Interface: Abs Sync WebService (Req and Res)
2. Transformation:
Interface Mapping: Abstr Async Webservice req and BAPI 1 request
Source Msg: Abs Async Web Service Request
Target Msg: Abs Async BAPI1 Request
3. Send Synchronous:
Mode: Synchronous
Synchronous Interface: Abstract Sync BAPI 1 (Req and Res)
Request Message: Astract Async BAPI 1 Request
Response Message: Abstract Async BAPI 1 Response
4. Transformation:
Interface Mapping: Abs Async BAPI1 Response and
Abs Async BAPI 2 Request
Source Message: Abstr Async BAPI 1 Response
Target Message: Abstr Async BAPI 2 Request
5. Send Synchronous:
Mode: Synchronous
Synchronous Interface: Abstract Synchr BAPI 2
Request Message: Abstr Async BAPI 2 Req
Response Message: Absrt Async BAPI 2 Res
6. Transformation:
Interface Mapping: Abstr Async BAPI 2 Response and
Abstr Async Web Service Response
Source Message: Abstr Async BAPI 2 Response
Target Message: Abstr Async Web Service Response
7, Send:
Mode: closes Sync Async Bridge
Message: Abstr Async Web Service Response
I have configured two adapters, once is SOAP and the othr RFC. In the RFC communication channel, I have checked the option of committing the BAPI.
Now when I test this scenario with XML spy, it gives me an error saying PL_TIMEOUT. FYI, cache refresh is upto date and also message are coming into the BPM.
Could anybody please let me know, whether its a problem with design of the BPM or anything else need to be checked?
Thanks,
Sumamight be the issue will be with the response mapping.
-
Hi,
I am using Sync/Async bridge in BPM and I am getting the below error.
We are in SP level 13.(PI 7.0)
Just I used the following steps (Receive (Open S/A bridge)-> Send(Sync) ->Send (Close S/A bridge))
If I test the my flow from Syncronus send step onwords it's working fine. When I send the message from my Outbound Interface i'ts givign me error.
While receving message receive step itself it's giving the error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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>
and also I did the following settings in SXMB_ADM.
Category : SA_COMM , Parameters :CHECK_FOR_ASYNC_RESPONSE_TIMEOUT , CurrentValue : 120
Category : RUNTIME, Parameters :HTTP_TIMEOUT, CurrentValue : 180000
Appriciate help. Did any one faced this issue with SP 13 .
Regards,
Venu.Hi,
I have checked PIAFUSER is not locked.
and I am copying the my trace file also.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host =</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 172.22.0.252</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = PID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = VGOPAL</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = EE617940D04111DDB6B000096B2E80E7</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - paralle</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) paralle PowerShopper_OB_aBS_Sync</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: PowerShopper_OB_aBS_Sync</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST End of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 003</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 004</Trace>
<Trace level="3" type="T">Message version 004</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-bs_ps</Trace>
<Trace level="2" type="T">-paralle</Trace>
<Trace level="2" type="T">http://multiplecalls.PowerShopper_OB_aBS_Sync</Trace>
<Trace level="2" type="T">create outbound binding for Process Engine</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for Process Engine: PE</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = SA_COMM</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_SA_BRIDGE_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="SA_COMM">
<Trace level="1" type="T">Start Sync/Async Communication</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:28Z CST Starting Processing</Trace>
<Trace level="1" type="T">Pipeline Timeout: 12/22/2008 10:04:29 CST</Trace>
<Trace level="3" type="T">Calling BPE Adapter</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">set corresponding asynchron interface PowerShopper_OB_aBS</Trace>
<Trace level="3" type="T">created BPE proxy for message EE617940D04111DDB6B000096B2E80E7</Trace>
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="3" type="T">reset to synchron interface PowerShopper_OB_aBS_Sync http://multiplecalls</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:29Z CST qRFC raised on XBQO$PE_WS90100031</Trace>
<Trace level="3" type="T">setting SA BPE state to wait for EE617940D04111DDB6B000096B2E80E7</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:30Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:31Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:32Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:33Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:34Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:35Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:36Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:37Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:38Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:39Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:40Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:41Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:42Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:43Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:44Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:45Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:46Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:47Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:48Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:49Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:50Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:51Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:52Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:53Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:54Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:55Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:56Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:57Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:58Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:02:59Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:00Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:01Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:02Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:03Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:04Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:05Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:06Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:07Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:08Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:09Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:10Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:11Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:12Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:13Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:14Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:15Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:16Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:17Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:18Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:19Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:20Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:21Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:22Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:23Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:24Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:25Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:26Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:27Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:28Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:29Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:30Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:31Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:32Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:33Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:34Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:35Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:36Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:37Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:38Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:39Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:40Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:41Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:42Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:43Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:44Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:45Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:46Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:47Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:48Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:49Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:50Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:51Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:52Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:53Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:54Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:55Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:56Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:57Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:58Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:03:59Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:00Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:01Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:02Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:03Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:04Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:05Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:06Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:07Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:08Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:09Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:10Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:11Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:12Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:13Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:14Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:15Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:16Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:17Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:18Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:19Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:20Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:21Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:22Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:23Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:24Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:25Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:26Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:27Z CST Wait time starting.</Trace>
<Trace level="1" type="Timestamp">2008-12-22T16:04:28Z CST Wait time starting.</Trace>
<Trace level="3" type="System_Error">Pipeline Timeout at 12/22/2008 10:04:29,7741240 CST</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
and the response message is showing the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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>
Regards,
Venu. -
PL_TIMEOUT in Sync Async scenario using BPM
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>Hi venkat,
These Threads will help you.
"PL_TIMEOUT" error
Help on PL_TIMEOUT error in BPM
Reward points if usefull... -
Hi all,
i am facing one error in SXMB_MONI.
The scenario is Sync-Async Bridge using BPM,request is successfully processing from XI but response case getting error in SXMB_MONI like pipeline timeout error at call Adapter.can anyone help me in this.
BestRegards
Venkatagirimake a search on sdn this is a very common issue in sync/async bridge (using BPM) scenarios...
PL_TIMEOUT in Sync Async scenario using BPM
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true
Create BPM in synchronous mode please help -
User getting locked while sending message sync via BPM. Please help
Hi Experts,
I have a sync - sync scenario where I am sending data synchronously from webservice to a sync RFC FM. I am using BPM and in BPM I have three steps
1. Receive step - Opens Sync-Async Bridge
2. Sync Send step
3. Send step - Closes SYnc-Async bridge.
This BPM solution is same as that give in the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
When I test this scenario I am getting
<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>
When I check the "Status monitor for Sync/Async communication" via SXMB_MONI, I found that my message is listed there with BPE status = "Wait".
On double clicking my message I found that there is an error " User is locked. Please notify the person responsible".
Why is my BPE struck in "Wait" stage and user is locked?
What am I doing wrong? Am I missing any settings in SOAP sender communication channel?
Please help me in resolving this problem.
Regards
GopalHi,
Few months ago we had also problems with "locked user" in XI, in our case XIAPPLUSER was sometimes (b)locked.
Perhaps note:
721548 Changing the passwords of the XI 3.0 service users
will help you.
We removed and entered the service users again, with the password in CAPITALS and language blank.
After that our problem was solved, I hope yours too.
Regards
Jack -
Sync/Async brdige error in BPM
Hi,
I am working on RFC-TO-Webservice scenario(Synchronous) and I am using the BPM in this scenario.
In BPM just I have used 2 steps.
Receive - Opened Sync/Async bridge
Send - Synchrouns step
Send - Cloase the Receive step
Send - Asynchrous send step (to send the response to the file...).
When I sent my RFC message from R/3 I am getting following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <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 am using PI 7.0 SP13 is why I am not able to receive the Sync message in BPM...I have created the abstract interface based on RFC...getting the first message itself Timeout error.
I am trying to use Sync/Asnc bridge in BPM. First message itself PL_TIMEOUT error..bpm is not able to receive my rfc request...
I need help on this...do I need to do any settings in WEBAS level..I did Timeout setting in SXMB_ADM.
Regards,
Venu.hi,
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
check this blog..and same thing I did in my scenario
my scenario is RFC-TO-Webservice.
Sync/Async bridge can't we use like this ...Receiver step(open sync/async)-> Send(Synchronous)-Send(Close sync bridge)....that way can't we use ...
I am not able to receive the RFC request itself inside my BPM first step...getting the Timeout error.
But when I use the RECEIVE STEP with Asynchronous mode..I am able to receive the message inside my bpm.Incase of Synchronous I am not able to receive the message..
I am working PI 7.0 and SP13..did any body worked this version...
Thanks,
venu. -
Hi all,
I am doing RFC to SOAP scenario using BPM.Each time when I run the scenario it is going for inbound queue (smq2) and I am getting PL_timeout error (Timeout condition for pipeline reached) . Please help me in resolving this issue.
Thanks and regards
SenthilHi Senthil,
This is the most common error that occurs during the BPM scenarios ,The following link discuss the same error.
PL_TIMEOUT error for BPM scenarios
Thanks,
Ram. -
** Throw Exception in BPM - Webservice to JDBC
Hi friends,
I am doing Webservice to JDBC scenario using BPM. I am doing insert data in backend system oracle table by passing inputs from WebService. After insert data in table, JBDC returns the response to web service thru response variable 'insert_count = 1' like this. When I try to insert the same record, that is, employee no as primary key in my table, XI throws an error 'ORA-00001 - unique constraint' in Addtional . We have to pass this information to Web Service. How will we achive this ?
Presently in our BPM design,
1) Exception property of the block as 'Error'.
2) Inside Block, in Sync Send Step (BPM -> JDBC) specified 'Exception/System Error' as 'Error'.
3) Inserted one Exception Handler Brach. In this Brach, inserted one control step. In this step, itself we put a Control Step, the action property of this step is 'Throw Exception'. Here , what we need to set for the 'Exception Property' ..?
Kindly help me friends.Hi Mahesh,
I refered those scenarios. But, our requirment is we want to take 'Additional Text' option from SXMB_MONI and map to WS source structure one element.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <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>TIME OUT REACHED</SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Timeout condition of pipeline reached
</SAP:Stack><SAP:Retry>N</SAP:Retry></SAP:Error>
Could you kindly help me ? -
Sync Web Service - BPM with 2 sync proxy calls error.
Hi.
Have a sync web service going into a BPM.
In the BPM there ar 2 sync calls towards a system making a credit check.
The answer is responded to the web service.
In our QA system the solution works perfect.
I transported the solution to production and when I test the web service call towards I get the following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Does anybody have an idea why I get the error.
When I check my config everything looks the same.
Looks like we never send the first sync call to the proxy when I check in SXMB_MONI and the BPM gets terminated.
We have just migrated the solution from XI 3.0 to PI 7.11.
BR
KalleHi.
How will that help if we do not send the message.
When I check the graphics in SXMB_MONI the error occours befor we send the first message with proxy.
Also extend ASYNC timeout?
We are using sync communication.
BR
Kalle -
BPM Sync/Async Scenario: error: "Timeout condition of pipeline reached"..!
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.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 -
BPM Error: Timeout condition of pipeline reached- After transporting to Prd
Hi,
I am doing Sync/Async BPM scenario.
-> Receive message and process it and send to BI and response has to send back to the sender.
start ->Receive(Request)> Transformation(Responsemap)>Send(SendtoR/3)->Send(Send Response) ---> stop.
It is working correctly in Test system. We transported to production and we are getting the below 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 crossed checked with the test system configuration and evything looks similar. Moreover there are someother Sync/Async BPM scenarios which are all working perfectly.
Kindly help me , What might be the reason. ?
Thanks
Deepthi.Some of the trace:
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
- <!--
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!--
-->
- <Trace level="1" type="B" name="SA_COMM">
<Trace level="1" type="T">Start Sync/Async Communication</Trace>
<Trace level="1" type="Timestamp">2009-08-17T04:48:09Z AUSNSW Starting Processing</Trace>
<Trace level="1" type="T">Pipeline Timeout: 17.08.2009 15:08:10 AUSNSW</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface OS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/FOC/DirectSales/Payments</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface AS_Payment</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/SAP_PI/DirectSales/Payment</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace> -
BPM when both sender and receiver systems are Sync. Please help!
Hi Experts,
I want to use BPM when both sender and receiver systems are Sync. For example: web service ---> RFC
I have tried the solution as given in the blog
https://weblogs.sdn.sap.com/pub/u/39730 [original link is broken] [original link is broken]
but it does not work. I am getting Time Out error.
Can somebody tell me the correct way of configuring BPM for sync-sync scenario?
Kindly give the integraion directory steps also.
Thanks
GopalHi Hemant,
I have already tried the solution as given in the blog (https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken])but it does not work. When I run the scenario I am getting Time out 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>
Please help!
Thanks & Regards,
Gopal -
Hello,
I want to receive a XML message from a HTTP sender synchron into a BPM.
In the BPM I have to to several steps, one is a mapping step and another is an asynchronus SEND of an IDOC to an R/3.
I have setup this BPM and everything works ok.
The BPM sends a HTTP-200OK back and a response message.
But in some cases the mapping step throws an exception. e.g. a mandatory field is missing.
In this case the HTTP-500 ERROR code is sent back, but with the response message
"Internal Server Error
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>INTERNAL.PL_TIMEOUT</SAP:Code><SAP:Stack>Pipeline timeout condition satisfied</SAP:Stack></SAP:Error>"
If I handle the exception in an exception branch everything work ok again, but then the HTTP-200OK is sent back.
Now my question:
How can I send back an HTTP-500 ERROR code from this synchronous BPM with my own response message.
I have tried with CONTROL STEP-CANCEL PROCESS, but I also get the same missleading error message back for the TIMEOUT. Also in this case the process is canceled after 60seconds with this timeout error.
Is is possible to send an HTTP-500 ERROR status and to cancel the process immediatly?
If yes, how can I set a specific RESPONSE message?
best regards
Werner MagerlHello Udo, hello Werner,
for the moment i am not sure but i think if i want to use a mapping i need a xsd that i have imported to my scenario, haven't i? (defined in MessageType?)
and other question: if i have a javamapping infront of the real mapping and this mapping throws an exception: can i catch this javamapping-exception and put this into the second transformation?
thanks a lot
Alex Schramm
Message was edited by: Alexander Schramm (18:36, 31.03.2006) -
Hello everybody,
we poll via file adapter. The files we read are processed in BPM.
Is it possible to access the value of a file name in BPM?
Regards MarioHi Mario,
yes,
set the Set Adapter-Specific Message Attributes indicator at communication channel and choose file name to store adapter attribute "file name" in the message header of the XI message. Map the value into the message to have it at BPM containter.
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm">SAP Library: Configuring the Sender File/FTP Adapter</a>
Regards,
Udo
Maybe you are looking for
-
A Toplink Java code example in Jdev 10.1.2
Hello every body I have just begun using Toplink 10g in Jdev 10.1.2, and I want examples of Java code to insert, edit and show information from struts application whose model is Toplink. Thanks
-
Execute Transaction from 4.6 SAP release
Dears, I have to execute MII trasactions from SAP but my release is a 4.6. I have already implemented such interface but between MII and SAP EEC6 relaese by using HTTP service. In 4.6 release the class I have used in the ECC6 version (cl_http_client)
-
I installed the trial version of FlashPaper. Tried printing 80 pages from PageMaker 7.0. After 1/2 hour of working I just gave up. Then I tried a simple 2 page file from PM 7.0. Same results after 15 minutes. Then I drag-n-dropped a 2 page PDF into F
-
Thumbnail caches-where are my photos?
On an upgrade, newly installed iphoto 6, I was asked or recommended to create thumbnails of my photos. I checked the "create now" box and now I see only the outline of my photos in the library with no pictures inside. I seem not to be able to reverse
-
Hi Friends! I am trying to publish a flash file which has 3 scenes. After Publishing its generates three SWF fils. I need single swf. Please help me! i am using flash 8 pro. Thanks in advance!