Code 110 Reason Error in HTTP Receiver adapter

Hello
I am having proxy to HTTP Receiver scenario in which i am calling the target application URL through HTTP Receiver Adapter. This interface is async interface and hence i am not expecting any response from the target system.
When i execute my interface the target system receives data from XI but in SXMB_MONI it sets the status of the message as "Automatic Restart" with the error description as "HTTP client. Code 110 reason" in HTML Code area <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
This is causing multiple messages stuck in the queue and presently i am manually clearing all the messages.
i checked the quality of service of the incoming message which is correctly setted as Exactly Once.
Is there any configuration missing?
Thanks in advance.
Regards
Rajeev

Hi Rajeev,
1.)Check in SMICM if your HTTP service is running or not.
2.)If its running fine then you can check whether your SSL certificate is configured properly or not.
Also follow the below mentioned links :
HTTP 110
HTTP Receiver Adapter -> HTTP client code 110 reason error when sending
*Pls reward with points if helpful*
Regards,
Shibani

Similar Messages

HTTP Receiver Adapter - HTTP client code 110 reason error when sending

Hi,
I am getting the following error when using the HTTP adapter as a receiver to perform an HTTP Post in a destination system :
<?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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Does anyone know what causes this error and more importantly how to trace it ?
Cheers
Colin.

hi Colin,
Check in SMICM if your HTTP service is running. Also in RFC destination one of the parameter (SSL client Certificate) might be wrong which could also cause this problem.
Also check this thread:-
XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Have a look into this SAP Note - 897583
Regards.
Praveen

ICM_HTTP_TIMEOUT error in HTTP Receiver adapter

Hi
I am doing HTTP Receiver adapter and File Sender adapter for my scenario.
I am getting the following error in SXMB_MONI.
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>402</SAP:P1>
<SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error
Help needed,

Hi Ganesh,
Check this weblog...
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Check this thread with similar issue...
ICM_HTTP_TIMEOUT
Regards,
Sridhar

Error in Http Receiver adapter.

HI Everyone,
I am doing File to HTTP Scenario.
I am Getting error as "ICM_HTTP_CONNECTION_FAILED" when i check in message monitoring.
What could be the problem.
Regards,
Varun

Hi,
Your error code is 400, so check this link,
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
For hhtp 400, its a bad request,
'The request could not be understood by the server due to malformed syntax.'
If you have the xi troble shooting guide see from page 54,and also try,
1.Check that the port really is the ICM HTTP Port (transaction
SMICM) and not the J2EE port
2.If the port is wrong, change the pipeline URL in the SLD in
the business system of the Integration Server
3.Restart the J2EE Engine to reset the SLD buffer of the
Adapter Engine
Source- "Xi troubleshooting guide"
or
1. try question 14 (integration engine section)
Finally Best of SDN 2005
2. also question 11 (in the same section)
3. if the avove will not fix it open xi config guide and
have a look at section
"Connecting Business Systems with an Integration Engine to the Central Integration Server"
did you complete all the steps?
BTW
but do the 1,2 steps in the first place:)
"Award points if helpful"
Regards,
Jayasimha Jangam

Error in scenario "FILE to HTTP(with SSL)" - HTTP client code 110 reason.

Hi friends,
Our scenario is as follows:
We are trying to send XML file from our SAP-XI to external tool "COMMunix XC" (a multi-protocol EDI platform tool).
We have configured " FILE TO HTTP(with SSL)" scenario (trying to connect HTTPS/port)
1. We have created RFC destination of type G and refered the same RFC in Communication channel (Adapter type: HTTP)
2. We have send the SSL Server certificate to other party and ensure that they have imported at thier end.
3. We have included the certificates from other party in our SAP XI STRUST under SSL Client (Standard) node.
4. We have tried " CONNECTION TEST " in the RFC destination created in type G (in STEP 1) and it shows the GREEN TICK at bottom, no other message nor any error message
When we trigger the communication we recieve the error: HTTP client code 110 reason in SXMB_MONI.
Please let us know if we have missed out some step.
What does error message indicate,
Regards,
Rehan

Hi Rehan,
I see that the PROCTIMEOUT was already at a very high value.
Does this occur for messages of a particularly large size? If yes, you could increase the parameter
icm/HTTP/max_request_size_KB = 2097152
This would need to be done in the sender/receiver system as well as XI.
Otherwise you could try reproducing the issue and checking the dev_icm log in the work directory, or go to SMICM -> Goto -> Display trace file
check for errors like NIECONN_REFUSED or "no service for protocol HTTPS" which can often be related to this type of issue.
Kind regards,
Sarah

PI/XI: "HTTP client. Code 110 reason" for XML PO transmission

PI gurus,
We use XI to convert PO IDOC to XML message and send the XML message to our vendors.
We got the error message "HTTP client. Code 110 reason" for two POs while other POs went to the same vendor successfully.
We also have no problem for sending XML POs to other vendors.
Is this error caused from the sender or the receiver and how can I fix the problem?
Thanks in advance!
Fisher

Hi,
Below link will help
HTTP client code 110 reason
For reference check the below links too
Message not reaching Integration server
HTTPS Receiver Adapter with POST and query String

HTTP Client : Code 110 reason

hi,
when i try to send a IDOC to XI to HTTP Receiver.
The flag shows red in the SXMB_MONI and the error is HTTP Client : code 110 reason message.
I am using a HTTP adapter for a HTTPS url as a receiver.
If i test the xml from a WFETCH i get a response saying no cXML Sent but there is cXML that i am adding in the Header body.
I have not used HTTP Client.
Any tips.
Thanks,
Tirumal

Hi Tirumal,
you were going correct man ...
The 400 error that you are getting can be because of :
The verb used in the request is invalid.
The requested URL is invalid.
The requested header name is invalid.
The requested hostname is invalid.
The request contains an invalid carriage return and/or line feed as a terminator.
The request contains an invalid content length header or invalid entity chunk length.
The cumulative length of the headers in the request is longer than the maximum allowed.
The header field in the request is too long.
The request header is too long.
Check on these lines and see if your problem is solved.
Rgds
joel

How to trace HTTP receiver adapter error

Hi All,
My scenario is to send PO details to vendor site (HTTPS URL). MY SSL configuration is complete and I have used the SSL certificates in RFC destination of type 'G'. When I test RFC destination connection, it gives me the correct response as '200'.
This RFC destination is used in HTTP receiver adapter of XI to connect to site and post PO xml document. It is passing successfully through Integration Server, as I get success flag in 'SXMB_MONI'. But, it is not reaching our vendor's site.
Can someone help me, with what's going wrong, or how can I trace the error.
Thanks & Regards,
Amit

Hi Sadhna,
It's a B2B scenario, where my sender is configured correctly and the receiver as well.
In sxmb_moni, I am getting successfull status. But, it is not reaching receiver.
Thanks & Regards,
Amit

When i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

when i send a test message throw the RWB for Http receiver adapter it is giving the error "Error in processing caused by: com.sap.aii.adapter.http.api.HttpAdapterException: ERROR_SOCKET_TIMEOUT, Read timed out"

Hi, Michal
I have read your Weblog. It makes sense to me. Thanks a lot for your help! However, I still have some questions and listed them as following. Could you please help to answer them?
Q1: I am new to SAP-XI. So I have no idea about TCODE-SXMB_ADM. Could you introduce more details about it?
Q2: The XI system I am using is running on SAP-ICC's machine. The tools I can use are:
1.Builder for Integration Repository
2.Builder for Integration Configuration
3.System Landscape Directory
4.Runtime Workbench
5.Administration System (for Repository, Directory, Runtime)
Please note that I do not have a complete control on this SAP-XI. Do you think whether or not I can set the timeout parameter by following the instructions provided in your Weblog?
For more details about my SAP-XI, please access the following Web page:
http://iccxi.sap.com:58000/rep/support/admin/index.html
Q3: The following messages are extracted from the SAP-XI. Wish they are hepful to solving my problem.
2006-06-19 05:12:16 Success The message was successfully received by the messaging system. Profile: XI URL: http://iccxi.sap.com:58000/MessagingSystem/receive/AFW/XI
2006-06-19 05:12:16 Success Using connection AFW. Trying to put the message into the request queue.
2006-06-19 05:12:16 Success Message successfully put into the queue.
2006-06-19 05:12:16 Success The message was successfully retrieved from the request queue.
2006-06-19 05:12:16 Success The message status set to DLNG.
2006-06-19 05:12:16 Success Delivering to channel: ValidationRequestHandlerServiceChannel
2006-06-19 05:12:16 Success SOAP: request message entering the adapter
2006-06-19 05:12:37 Success SOAP: call failed
2006-06-19 05:12:37 Error SOAP: error occured: java.net.ConnectException: Connection timed out: connect
2006-06-19 05:12:37 Error Exception caught by adapter framework: Connection timed out: connect
Thanks
Menghua Li

HTTP Receiver Adapter

Hi,
I am working on a scenario, where I am posting xml message on https url, for which I am using HTTP receiver adapter.
I have created RFC destination of type 'G' in sm59 to make an https call, where I have provided following details:
In Technical Settings:
Target Host - <Hostname>
Service No. - 443
Path Prefix - <url path>
Logon Security:
SSL - Active
SSL Client Certificate - Default SSL Client (Standard)
UserName - <Username>
Password - <Password>
I have used this RFC destination in 'HTTP Destination' of HTTP receiver adapter.
When I test this interface, I am getting this error.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 110 reason</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Can you please help me resolve this issue. Please let me know, if I am following the right steps.
Thanks in advance
Regards,
Amit

Hi -
Since you're using the http destination option in the channel, you just specify the user/pwd in the destination.
Regarding the issue, first, for the Logon/Security option in the destination, unless you'll be using a client certificate to authenticate, you should choose option ANONYM SSL Client (Anonymous) - you still provide the user/pwd in the Logon section. Make sure you have imported the root cert of the CA verifying the server's identity into the client certificate list within STRUST (node SSL Client (Anonymous)).
Also, for some hints on the issue, look at the ICM trace - tcode SMICM->Goto->Trace File... you may need to increase the trace level - SMICM->Goto->Trace Level... After resolving the issue, make sure to set the trace level back to default.
Regards,
Jin

HTTP Receiver Adapter - delete ?xml version="1.0" encoding="UTF-8"?

Hi,
Is it possible to delete the part below when sending an HTTP request through HTTP receiver adapter without any java/abap/xslt mapping?
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
Thanks
Arman

Hi,
<?xml version="1.0" encoding="UTF-8"?>
Specifies that the given message is xml
<ns0:MT_SELL xmlns:ns0="http://test.com/Sell">
Specifies its a MessageType of the payload, without this that message is not identifies and is not processed. Its manditory to have these. Other wise error will raise.
Regards,
Prasanna

How to set HTTP header field "cookie" with http receiver adapter?

Hi,
I am using http receiver adapter (not axis) in a scenario. I could not set a parameter with key cookie in http header. Is there some kind of restriction to set it? I am able to set others like connection and create custom fields using ASMA and dynamic key configuration via UDF on mapping.
Could you please comment on, is cookie http parameter special or noneditable by PI's http adapter? I am looking for a solution without editing any abap code...
Regards,

I believe it is possible since axis adapter provides very same functionality. Let me summarize my scenario may be it helps:
I am trying to call series of webservice lets say in a BPM. First service (login service) will provide me with a session id (in http header with key Set-Cookie) then I will call another service which has that session id in its http header with key cookie then I am going to logout. So I am testing the second part now, but it doest let me send cookie http header parameter.
I hope I clarified a bit more my problem.
Regards,

Adapter specific properties (http receiver adapter)

Hi,
does anybody know the technical name for the HTTP destination of a http receiver adapter.
The documentation lists only the names URLParamOne to URLParamSix and HeaderFieldOne to HeaderFieldSix.
Neither the technical name for URL nor for a HTTP destiantion are mentioned.
Regards,
Marc

Hello Moorthy,
I know this part of the documentation.
So I set the indicator within the communication channel.
Now, I have to fill the dynamic configuration during my mapping. My code looks like following:
DynamicConfigurationKey keyURL = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP", XXXXX);
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) param.get (StreamTransformationConstants.DYNAMIC_CONFIGURATION);
// set value
conf.put(keyURL, url);
So what has to be filled instead of XXXXX ?
Regards,
Marc

HTTP Sender and HTTP Receiver adapter. Pls advice urgent

Hi All,
There is one Third Party that wants to send XML data and receive XML data with XI.
Please let me know can I use HTTP for that.
How to use HTTP Sender part?
How to use HTTP Receiver Adapter?
Pls send blogs/doc for that
Thanks and Regards

hi.,
Check this thread for the code for a HTTP Client,
/message/266750#266750 [original link is broken]
Also, check these blogs. They use HTTP adapters for their configuration,
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Check these links for the configuration part.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Weblog :
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
note:reward points if solution found helpfull.....
regards
chandrakanth.k

HTTP Receiver Adapter : Dynamic URL

Hi,
I have a scenario where I wish to build a dynamic URL for the HTTP Receiver Adapter. The URL will contain a customer number which is present in the mapping.
The help seems to suggest that this is possible :
If you want to use an HTTP destination or URL set by the mapping, set the URL or HTTP Destination indicator. (The indicator displayed depends on the Addressing Type you selected above). If you set the indicator, the URL or HTTP destination set dynamically is called by HTTP.
If the message header does not contain the URL or the HTTP destination, and you have set the Fail If Adapter-Specific Message Attributes Missing indicator, the XI message is set to status System Error. If you do not set the indicator, the URL or HTTP destination defined statically in the communication channel is used.
However, it is not very clear where the URL needs to be set dynamically.
Does anyone know how to achieve this ?
Cheers
Colin.

hello to all,
We have a unique issue with one of our customers that is limited to 100 character URL. The current url is http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck&interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
Is there a way to have a URL like
http://mycompany.com/sap/xi/adapter_plain?namespace=urn%3Agoodyear%2Ecom%3AAIT%3AInventoryCheck
and then somewhere in the process add... &interface=AITInventoryCheck_Abs&service=HTTP_AIT_InvChk&QOS=BE&sap-client=010&sap-language=EN
So the data comes to an F5 through the DMZ to the SAP webdispatcher then to the SAP XI system.
Any ideas if this is possible or how you could start with a shorter URL?
Thanks,
Dede

Code 110 Reason Error in HTTP Receiver adapter

Similar Messages

Maybe you are looking for