Skip to Content
Author's profile photo Krishna Moorthy P

Http* Errors in XI

There are many forum discussions about Http Errors. This blog is collective information about most common HTTP errors occurring during XI implementations and possible tips to solve the problems.

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

Reference: For Http code description– -> Operations -> SAP XI -> Troubleshooting Guide – SAP XI 3.0/2.0.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Hi Krishna,

      This is a real good one, good complied resource of all the HTTP errors in one place.

      I realy appreciate this.

      keep up the good work.


      Author's profile photo Michal Krawczyk
      Michal Krawczyk
      Hi Krishna,

      I added your nice weblog to the XI FAQ
      (question 34 - Ingration Engine section)


      Author's profile photo Krishna Moorthy P
      Krishna Moorthy P
      Blog Post Author
      Hi Michal,

      Thank you very much for the same.


      Author's profile photo Jawahar Govindaraj
      Jawahar Govindaraj
      It is really helpful one.
      Jawahar Govindaraj
      Author's profile photo Kavita Laddha
      Kavita Laddha
      Its really a good blog.


      Author's profile photo Former Member
      Former Member

      This is really a good one.......


      Author's profile photo Former Member
      Former Member
      Hi Krishna,
              Great blog...
      I have this scenario proxy-XI-jsp thru HTTP adpter .Now there are some problems in my receiver communication channel which uses HTTP adapter and I am getting status code:1250 ..and message as request parameter is null..any idea what could be the problem.Actually the jsp page has a textarea'test' and a submit button.After ntering this inputfiel'test' and clicking on submit it calls handler /abcdef/trial' now same thing Iam trying out using HTTP adapter so when in the prolog I have give test= so after the request is sent, in SXI_MONITOR I see reaponse as status code 1250 and message -> HTTP request parameter [test] is null.any Idea  y I am getting this error...?
      Author's profile photo Former Member
      Former Member
      to solve this try in the INTEGRATION_DIRECTORY_HMI destination put in the path field /dir/hmi_cache_refresh_service/ext
      Author's profile photo Former Member
      Former Member
      Good answer
      Author's profile photo Martin Steinberg
      Martin Steinberg

      what about the http response code 110.

      I get lot of errors in SAP Exchange Infrastructure in SXI_MONITOR:

        Error when receiving by HTTP (error code: 110, error text: )

      Any idea?

      With kind regards.

      Martin Steinberg

      Author's profile photo Former Member
      Former Member
      Ever so often, the outgoing message ends in error with the message for ONLY 1 vendor:
      ICM_HTTP_CONNECTION failed - HTTP client. Code 400 reason
      The soft restart of the ICM monitor helps to eliminate the issue.
      I have gone through your blog and it is great but nothing is mentioned about the above error code.
      I checked the SAP Notes that you have mentioned but nothing says about the same.
      Can you plesae advice?