cancel
Showing results for 
Search instead for 
Did you mean: 

Error in file-file scenario: HTTP response contains status code 503

Former Member
0 Kudos

Hi folks,

I've encountered the foll error in file-file scenario:

Testing file-file scenario (followed the blog: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&)

Initially i was hving problems with recvr comm channel, which are now resolved. File is sent successfully but not recvd. I tried to modify the scenario above and change the file type to 'Text' but still got the same error.

I've checked SICF -->default_host/xi/engine , we dont maintain logon data there. when i test the default_host/xi/engine service, it resolves into an ip addr as follows:

http://<hostname>.<domain.com>:8001/sap/xi/engine?sap-client=<clientNo>

(Also, we hv a BW system running on the same server ,which uses a fully qualified domain, while we dont which is why we get the above domain. Im not sure if there are any issues with that.)

and we get the foll error:

Error Code 10060: Connection timeout

If i remove the domain manually, im prompted for userid/pwd and get the foll result:

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header />

- <SOAP:Body>

- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<faultcode>SOAP:Client</faultcode>

<faultstring>Pipeline specified in URL attribute (type) not existing</faultstring>

<faultactor>http://sap.com/xi/XI/Message/30</faultactor>

- <detail>

- <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">URL_PIPELINE_NOT_FOUND</SAP:Code>

<SAP:P1>/sap/xi/engine?sap-client=<clientNo></SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Pipeline ID , which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>

</SAP:Error>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

also, we dont hv any overload issues as this is dev env and not many of us are using the xi server. Would really appreciate if any of you can share your inputs on how to resolve this. Thanks!!

cheers

Prachi

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi ,

Look in to this for all errors

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.

Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active

• Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine

• The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.

• Refer SAP Note 803145,807000,791655

<b>Award Points if found usefull.</b>

Former Member
0 Kudos

hi dinesh,

ive already gone thru the existing blogs on the same issue, but that's not been helpful..also pls note the points in my post:

we dont hv ne overload issues. its a dev env..only a couple of users so far using xi

We've already attempted restart of J2ee engine.

pls help with any new tips that u might hv! thanx!

cheers

prachi

Former Member
0 Kudos

Do one thing

Try to test u r Configuration first.

Copy payload and paste in test configuration

lets see whats happening

Former Member
0 Kudos

Hey

make sure you have correct entry in IS_URL under tcode sxmb_adm

Thanx

Ahmad

Former Member
0 Kudos

Hey

make sure the pipeline URL in sxmb_adm is of the following form

In SXMB_ADM ->Integration Engine Configuration->Specific Configuration

Here IS_URL Value should be Http://Hostname:Port/sap/xi/engine?type=entry

where port is the HTTP port which you can find in SMICM->goto->services.

Thanx

Ahmad

Former Member
0 Kudos

hi ahmad,

is url is correct. i checked the config, it tested ok. i hv some dbts regd the sicf->xi/engine test..the ip add appends the domain, which we are not using..just wondering if thats the culprit. Any thoughts on that?

thanks

prachi

Former Member
0 Kudos

Hey

the URL you have for the pipeline is

URL = /sap/xi/engine?sap-client=811

and the URL must be of the form i suggested,even the error says no entry for <b>Type</b>

are you sure the IS_URL is correct:)

>><SAP:Stack>Pipeline ID , which is expected as value of attribute "type" in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>

This is the culprit

Thanx

Ahmad

Message was edited by:

Ahmad

Former Member
0 Kudos

how can i test the config? rwb or which txn?

thanx

prachi

Former Member
0 Kudos

In ID Tools--Test configuration.

Enter all values and press F5

Former Member
0 Kudos

thnx for the reply..

like i said, if i go to sxmb_adm and go to integration engine, the url indicated is correct, if i run a check on this, its successful

in sld, the pipeline url indicated is correct as well..

My nxt qn now is,

are there any pipeline ids to be maintained in txn sxmb_adm (under display pipeline definition)?

im not sure from where is it pickinp up the incorrect url..

Former Member
0 Kudos

Hey

well if you are sure that the Pipeline URL is correct,then you might wanna do a complete cache refresh using SXI_CACHE.

hope it helps

Thanx

Ahmad

Former Member
0 Kudos

Hey

are your ICF services activated?if not then do the following

goto transaction SE38 in XI and enter the program name as RSXMB_ACTIVATE_ICF_SERVICES and hit display,it will open a ABAP code which u have to activate,by clicking the activate button on the top.

Thanx

Ahmad

Message was edited by:

Ahmad