LOOP_IN_MESSAGE_ROUTING

Hi All,
- Scenario : BPM <-> Abap Proxy on R/3 (synchrone)
In the SXI_MONITOR (on both XI and R/3), I have the following message :
"Code : PROTOCOL.LOOP_IN_MESSAGE_ROUTING
Loop discovered in message flow: System is.00.sap001, pipeline IS with inbound adapter XI already run (see HopList-Property in SOAP"
What can I do?
Thanks in advance.

Hello Olivier,
Did you figure out what caused this ?
Regards

Similar Messages

XI Adapter LOOP_IN_MESSAGE_ROUTING (Inbound service interface PI- ERP)

Hello,
my scenario:
PI is sending some data via XI Adapter to ERP (SAP ECC 6.0).
In PI SXMB_MONI shows us LOOP_IN_MESSAGE_ROUTING.
Some points:
- Proxy is generated and activated in ERP
- ERP is type of LOC (application system)
- Corresponding Integ. Server of ERP is our specific PI
- ERP HTTP port is running (SMICM->Services)
- XI Adapter is using messag protocol XI3.0
- XI Adapter refers to an HTTP RFC destination
- PI HTTP RFC destination to ERP uses /sap/xi/engine?type=entry as path prefix
- testing the PI HTTP RFC responses with: Empty HTTP request received (as suggested)
- calling ERPserver:HTTPport/sap/xi/engine?type=entry in local web browser results in: EMPTY_HTTP_REQUEST_RECEIVED (as suggested)
So why our message is send back from ERP to the sender PI integration engine and fails with LOOP_IN_MESSAGE_ROUTING?
Thanks in advance,
André

Hi,
error occours after calling the XI Adapter in CENTRAL pipeline:
HTTP-client: closing... External error header received Error exception return from pipeline processing! CENTRAL</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack> Schleife im Nachrichtenfluss entdeckt: System is.00.sappi1a, Pipeline CENTRAL mit Inbound-Adapter XI bereits durchlaufen (siehe HopList-Header) </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Many thanks,
André
Edited by: André Schillack on Dec 6, 2010 10:56 AM

FILE TO INBOUND ABAP PROXY - " LOOP_IN_MESSAGE_ROUTING ERROR "

Hi ,
Getting the following Error in *FILE TO INBOUND ABAP PROXY* which is updating a Database table in R/3.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.01.lgscms</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How to rectify the Error..
Regards,
Ravi

Hi Ravi !
Check if the url for the receiver is
http://<host>:<port>/sap/xi/engine?type=receiver
or
http://<host>:<port>/sap/xi/engine?type=entry
if using XI 3.0
Regards,
Matias.
Edited by: Matias Denker on Feb 25, 2008 2:12 PM

IDOC stuck in PI with Loop error ( R/3 - PI - SCM SNC scenario)

Hi,
I am sending a PO as an IDOC from R/3 to SNC, the receiver side configuration was made with XI adapter with HTTP protocol. I am getting the IDOC received in PI but with below error. Any help is highly appreciated.
Aso I am not sure if the receiver communication channel should be XI server host and url or SNC host.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.23.saptest1</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText>Loop in message flow found: system is.23.saptest1, pipeline CENTRAL with inbound adapter XI already processed (see hoplist header)</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Menaga

Every one thanks for your reply, first I tried changing my communication channel parameters which I had the PI host name and port and now I changed to SCM host name and port with path prefix /sap/xi/engine/?type=entry...I got the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_SEND_FAILED</SAP:Code>
<SAP:P1>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while sending by HTTP (error code: 404, error text: Not Found) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Thanks,
Menaga

XI protocol error occurred in abap proxy scenario- plz

Scenario is asynchronous
Http -> XI ->R/3(abap server proxy)
sender: Through http client
receiver is abap server proxy
Repository objects:
Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)
Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)
Interface mapping: source=sender_MI, receiver_MI.
Proxy generated on R/3 client 550 for receiver_MI.
Configuartion objects:
Sender: business service, no comm channel since http sender.
receiver: R/3 business system
Comm channel: receiver_cc type of XI.
transport protocol: http
message protocol : XI 3.0, since both XI and R/3 on webas 6.4
addressing type: URL
target host: diamond
service number: 8005
path: /sap/xi/engine?type=entry
Authentiction data:
user name: user22
passwrod; correct
logon client: 400 which is the same client I developed ll the design and config objects.
Recevr determinaion, interface determination and recevr agrrement looks fine.
The error iam getting is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.05.diamond</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Please reply , your help is appreciated.
Thanks
KK

Stefan thanks,
I tried as you suggesetd putting the info of R/3 for
server: diamond
port: 8005
client: 550
user id: user05
pwd: correct
But I get the below error, suggest me what permission should this userid have?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

Abap proxy call failed

Hi,
I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.
Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,
an error occured on the R3 system:
PROTOCOL.LOOP_IN_MESSAGE_ROUTING
<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <SAP:Context></SAP:Context>
 <SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>
 <SAP:Text language="EN"></SAP:Text>
 </SAP:ErrorHeader>
 <SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">
 <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type></SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 <SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>3.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type></SAP:Type>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 <SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">
 <SAP:MessageInbound>
 <SAP:Type>IENGINE</SAP:Type>
 <SAP:AdapterRefId>2.0</SAP:AdapterRefId>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageInbound>
 <SAP:MessageOutbound>
 <SAP:Type>PROXY</SAP:Type>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 </SAP:MessageOutbound>
 </SAP:Hop>
 </SAP:HopList>
 <SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">
 <SAP:From>
 <SAP:Name>WebServer</SAP:Name>
 <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>
 </SAP:From>
 <SAP:To>
 <SAP:Name>UPG</SAP:Name>
 <SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>
 </SAP:To>
 <SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>
 <SAP:QualityOfService>BestEffort</SAP:QualityOfService>
 <SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>
 <SAP:Direction>Response</SAP:Direction>
 <SAP:Document></SAP:Document>
 </SAP:MessageHeader>
 <SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <SAP:AdapterInbound>PROXY</SAP:AdapterInbound>
 <SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
 </SAP:InternalAttributesHeader>
 </SOAP:Header>
 <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
 <SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">
 <SAP:Payload xlink:href="cid:[email protected]">
 <SAP:Document>TraceDocument</SAP:Document>
 </SAP:Payload>
 </SAP:Manifest>
 </SOAP:Body>
 </SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:[email protected]
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
 <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
 <Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>
 <Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</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="1" type="T">system-ID = UPG</Trace>
 <Trace level="1" type="T">client = 100</Trace>
 <Trace level="1" type="T">language = E</Trace>
 <Trace level="1" type="T">user = YLEBLEVEC</Trace>
 <Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>
 <Trace level="1" type="T">* * </Trace>
 <Trace level="1" type="T">* * </Trace>
 <Trace level="1" type="T">**************************************************** </Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
 <Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>
 <Trace level="1" type="T">PLNAME = SENDER</Trace>
 <Trace level="1" type="T">QOS = BE</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
 <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>
 <Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>
 <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
 <Trace level="1" type="T">URL for integration server read from global configuration </Trace>
 <Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>
 <Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
 <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>
 <Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>
 <Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>
 <Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>
 <Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>
 <Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>
 </SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END
I guess the error occurs before the call of my proxy. Can anyone help?
Thanks,
Yann

Hi,
>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?
I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right
further reference (XI configuration guide):
Connecting Business Systems with an Integration Engine to the Central Integration Server <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)
>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?
yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)
no need for a second client on R3 side:)
sorry if I confused you with my response
Regards,
michal
Message was edited by: Michal Krawczyk

Loop in message flow found

Hi all
I created a idoc to abap proxy for the xi adapter i used http destination with my destination defined in sm59.
In sxbm_moni i get the error:
LOOP_IN_MESSAGE_ROUTING
Loop in message flow found: system is.00.metsapxd, pipeline CENTRAL with inbound adapter XI already processed
Anyone know how to fix the error?
Thx

Hi,
I think your end business system i.e. where proxy exists -- this application system is configured as "integration engine/HUB". Try to keep it as (SXMB_ADM -> Integration engine configuration) type of business system as "applicaiton system" instead of integration engine/server.
Regards,
Rao.Mallikarjuna

LOOP_IN_MESSAGE_ROUTING

Similar Messages

Maybe you are looking for