Skip to Content

Sync Async bridge LOOP_IN_MESSAGE_ROUTING

Hi Sirs,

I'm currently working on a sync-async bridge for a SAP requirement. I used the solution provided by William Li in his blog regarding Responseonewaybean and RequestresponseBean modules. The setup is working fine everytime I trigger a message via runtime workbench. I'm having errors though when I'm testing end to end.


Our scenario is 3PL to PI via FILE async. then PI to an SAP system via SOAP sync. The response from SAP will be sent back to the 3PL. With this scenario, I'm currently getting a LOOP_IN_MESSAGE_ROUTING error.


Error message:

04/11/2016 08:36:02.953 Error Received XI System Error. ErrorCode: LOOP_IN_MESSAGE_ROUTING ErrorText: null ErrorStack: Loop in message flow found: system is.81.PI_sample, pipeline CENTRAL with inbound adapter XI already processed (see hoplist header)

04/11/2016 08:36:02.975 Error Transmitting the message to endpoint http://PIsample:xxx/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: LOOP_IN_MESSAGE_ROUTING:.


The sxmb_adm is configured already configured:

SAP_SAMPLE role of business system - Application system

Corresponding integration server http://PIsample😍xx/sap/xi/engine?type=entry

sicf configured for xi/engine


Business system in SLD configured already

SAP_SAMPLE role Application system

Related Integration server INTEGRATION_SERVER_PI

technical system SAP_SAMPLE client XXX

logical system name XXX


SOAP Receiver channel for the sap system has the module parameters for RequestResponseBean, ResponseOnewayBean passThrough, interface, interfaceNamespace, interfaceNamespaceOnFault, interfaceonFault, replaceInterface, replaceInterfaceonFault and is connecting to http://sap_sample:xxxx/sap/xi/engine?type=entry

message protocol is XI 3.0 and has username password for authentication


SOAP sender channel for the sap system has SOAP 1.1 message protocol


When Runtime workbench is used to trigger the message from 3PL, the response file back to 3PL is working perfectly. When the file is triggered via FILE, the LOOP_IN_MESSAGE_ROUTING is encountered. any thoughts sirs?

Message was edited by: SAPenthusiast SAPenthusiast

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Apr 12, 2016 at 03:11 AM
    10

    Hi SAPenthusiast (whoever you are)

    Please check the target URL on your SOAP receiver system. From your error message, maybe the URL is looping back into the PI system instead of the backend SAP system.

    Regards

    Eng Swee

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 12, 2016 at 03:36 AM

    The one thing I can think of is to check the back-end SAP System. Is it running on a WAS 6.20 or >= WAS 6.40?

    If it is running on WAS 6.20 ( typically R3 4.7 ), then the URL would need to be  : sap/xi/engine?type=receiver

    Configuring the Channel for ABAP Proxy Receivers - Proxy Programming - SAP Library

    Also - when you say it works from Runtime work beanch, what are the parameters used in the RWB to trigger the message? Are you setting the QOS as Exactly Once or Best Effort?


    Regards,

    Bhavesh

    Add comment
    10|10000 characters needed characters exceeded

    • I tested it again just now using Integration engine component in the RWB and a response file was sent successfully in the specified folder.

      I'm thinking inconsistencies between adapter and integration engine but I cannot identify the specific proble.

  • Apr 12, 2016 at 12:21 PM

    Hi Sirs, connection errors seems to be in AFW. Please see logs below:



    successful response: 04/12/2016 11:31:28.367 Information SOAP: continued from request message 11111111-1111-1111-1111-1111111111111 04/12/2016 11:31:28.373 Information SOAP: response message leaving the adapter 04/12/2016 11:31:28.403 Information ROB: entering ResponseOnewayBean 04/12/2016 11:31:28.405 Information ROB: resuming the transaction 04/12/2016 11:31:28.408 Information ROB: sending to the messaging system ... 04/12/2016 11:31:28.409 Information The application tries to send an XI message asynchronously using connection AFW. 04/12/2016 11:31:28.432 Information Trying to put the message into the send queue. 04/12/2016 11:31:28.571 Information MP: leaving 04/12/2016 11:31:28.571 Information Message successfully put into the queue. 04/12/2016 11:31:28.571 Information ROB: leaving ResponseOnewayBean 04/12/2016 11:31:28.571 Information ROB: returned with no response 04/12/2016 11:31:28.571 Information The application sent the message asynchronously using connection AFW. Returning to application. 04/12/2016 11:31:28.614 Information The message was successfully retrieved from the send queue. 04/12/2016 11:31:28.659 Information The message status was set to DLNG. 04/12/2016 11:31:29.013 Information The message was successfully transmitted to endpoint http://PI_SYSTEM:11111/sap/xi/engine?type=entry using connection AFW. 04/12/2016 11:31:29.066 Information The message status was set to DLVD.




    wrong response: 04/12/2016 11:11:22.728 Information SOAP: continued from request message 11111111-1111-1111-1111-1111111111111 04/12/2016 11:11:22.730 Information SOAP: response message leaving the adapter 04/12/2016 11:11:22.745 Information ROB: entering ResponseOnewayBean 04/12/2016 11:11:22.747 Information ROB: resuming the transaction 04/12/2016 11:11:22.750 Information ROB: sending to the messaging system ... 04/12/2016 11:11:22.751 Information The application tries to send an XI message asynchronously using connection AFW. 04/12/2016 11:11:22.772 Information Trying to put the message into the send queue. 04/12/2016 11:11:23.500 Information MP: leaving 04/12/2016 11:11:23.500 Information Message successfully put into the queue. 04/12/2016 11:11:23.500 Information ROB: leaving ResponseOnewayBean 04/12/2016 11:11:23.500 Information ROB: returned with no response 04/12/2016 11:11:23.500 Information The application sent the message asynchronously using connection AFW. Returning to application. 04/12/2016 11:11:23.766 Information The message was successfully retrieved from the send queue. 04/12/2016 11:11:24.179 Information The message status was set to DLNG. 04/12/2016 11:11:24.417 Error Received XI System Error. ErrorCode: LOOP_IN_MESSAGE_ROUTING ErrorText: null ErrorStack: Loop in message flow found: system is.81.PI_SYSTEM, pipeline CENTRAL with inbound adapter XI already processed (see hoplist header)  04/12/2016 11:11:24.420 Error Transmitting the message to endpoint http://PI_SYSTEM:11111/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: LOOP_IN_MESSAGE_ROUTING:. 04/12/2016 11:11:24.471 Information The asynchronous message was successfully scheduled to be delivered at Tue Apr 12 11:16:24 GMT 2016. 04/12/2016 11:11:24.471 Information The message status was set to WAIT. 04/12/2016 11:16:24.441 Information The message status was set to TBDL. 04/12/2016 11:16:24.462 Information The message was successfully retrieved from the send queue.

    Add comment
    10|10000 characters needed characters exceeded