HTTP - Receiver - PLAINHTTP_ADAPTER Error

hi,
I have configured a HTTP Receiver. I get the following error in the SXMB_MONI - HTTP Client 110 Reason.
I set the Trace Level high using SMICM and looking at the log, it seems like its connecting to the host that i specified in the HTTP Receiver Adapter but at the end i get this error:
ERROR => PlugInHandleNetData: client: premature EOS - header not complete in response [http_plg_mt. 2470]
[Thr 13] PlugInHandleNetData: read response header
[Thr 13] PlugInHandleNetData: header termination not found
[Thr 13] PlugInHandleNetData: need more data (0/-1)
[Thr 13] IcmPlCheckRetVal: Next status: READ_RESPONSE(2)
Any idea why i am getting this error?
Thanks,
Tirumal

Moorthy -
I am seeing this error in the log file when i use the SMICM tcode.
I am getting the error while sending a request to the HTTP Receiver.
Let me know if you have more information.
Meanwhile, will go through the blog and see if i can do more troubleshooting.
Thanks,
Tirumal

Similar Messages

HTTP Receiver adapter error ?

HI Guys,
I have configured the IDOC-HTTP. I have defined a bsuiness service on the receiver side as the receiver is not in our landscape and he is our business partner.
I have created a RFC connection of type G and it is working properly but the HTTP reciver adapter gives the error as below
I'm getting an error when I go to "sxmb_moni" which says
Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER
Kindly help..
Thanks,
Raj
Message was edited by:
raj reddy

Hi Raj,
Error Category = PLAINHTTP_ADAPTER
Error ID = ATTRIBUTE_SERVER
as far as i know this problem is due to high traffic.When the data comes in bulk some of the message are failing or when they are not able to connect to reciever server.So it gives error.
u can look @ these threads of similer taste
PLAINHTTP_ADAPTER.ATTRIBUTE_SERVER error
PLAIN HTTP ADAPTER -ATTRIBUTE_SERVER ERROR
Plain HTTP adapter error
PLAINHTTP_ADAPTER - ATTRIBUTE_SERVER
and also look @
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
Regards
biplab

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

Http receiver adapter error : ICM_HTTP_CONNECTION_FAILED

Hi all.
I have set up a receiver http adapter and for the life of me can't get it to work. In sxmb_moni I get the following error in the Call adapter step of the pipeline:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client. Code 400 reason ICM_HTTP_CONNECTION_FAILED</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
It does not matter where I try and post to, it comes back with this. I am using "Url address" for Addressing type.
Help appreciated.

You should check whether the HTTP service is working on your system.
transaction smicm -> goto -> services. check the entry for HTTP. If necessary, a restart of the J2EE server might help.
Also check the http adapter is active.
transaction sicf -> default_host->sap->xi->adapter_plain
Cheers
Manish

Seeburger AS2 HTTPS receiver channel error

Hi,
I am getting the following error in the receiver Seeburger AS2 channel with HTPS connection and going through a proxy to the Partner.All the certificates have been installed,proxy server information gives,mentioned the key store values and encryption certificate values have been mentioned in the receiver agreement that is using the channel.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection., SEEBURGER AS2: HTTP-Client component init failed # java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: Could not retrieve alias collection.
Can you please give me an idea whether I am missing something or any configuration settings I need to make.
Thank you,
Sri

hi Neetesh,
Thank you for the link.The first thing I have looked at is the link you gave me.But when I give with * it is complaining that it is not able to retrieve the certificates.
TRUSTED/AS2CERTS/*,but I have backward slashes..may be OS is different ,I think the original poste might have Windows servers.
any other ideas please.
thank you.

HTTP Receiver interface returns with error code 110

Hi All,
We are posting the document from XI to a external server as HTTPS request.
We are able to sucessfully post the request to external server using HTTP destination as address type but not able to post sucessfully with URL as address type.
Here goes the details -
We are able to post the HTTPS request successfully on the external server using the HTTP destination as address type in HTTP receiver adapter setup.
When we setup address type as HTTP destination , we need to provide the following details -
IN SM59 , Connection type G
Target Host : host name ( with out "https://" as prefix)
Service No : 443
Path prefix : query string
SSL : Active
Certificate : Select the certifacte from the client certificate list.
We can post the request to external server using URL as address type in HTTP receiver adapter setup.
When we setup address type as URL , we need to provide the following details -
Address type : URL Address
Target Host : host name ( with out "https://" as prefix)
Service Number : 443 ( HTTPS port setup on XI)
Path : query string.
When we post the same request as we did with HTTP destination as Address type , we are getting a HTTP response code as failure HTTP response code 110
Please find the details about the return code -
If a cache returns a stale response, either because of a max-stale directive on a request, or because the cache is configured to override the expiration time of a response, the cache MUST attach a Warning header to the stale response, using Warning 110 (Response is stale).
110 Response is stale
MUST be included whenever the returned response is stale.
Please find the error message from SXMB_MONI
<?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>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>
Please let me know if some one has faced this issue.
Regards,
Reddy
Edited by: Nanda kishore Reddy Narapu Reddy on Mar 11, 2008 12:35 PM

Hi All,
Is some one can confirm that - We can use HTTPS with Address type as URL address in HTTP receiver adapter setup.
I can confirm that using HTTP destination as Address type in HTTP receiver adapter setup we can attain HTTPS communication with external server.
If some one who has tried HTTPS communication using HTTP receiver adapter using URL address as Address type can guide me what are the steps need to be done.
Address type is a parameter in HTTP adapter setup .
Regards,
Reddy

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

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

Queue error in HTTP receiver

I have a HTTPS receiver set up to send a file to the targer HTTP URL (external), file has been picked up but it's in queue with SYSFAIL status and message
XI Error ATTRIBUTE_CLIENT.PLAINHTTP_ADAPTER: Queue
Do I need to create a service in SICF for the web address?
Thanks,
Menaga

Hi, tahnks every one for your answers but I am still not able to get to it.
Checked with the customer and they didn't receive it, the same works with webmethods fine. I changed the communication channel with RFC destination type G instead providing the URL direct. I am gettign the below error.
Do I need any thing specific for HTTPS communicaiton in PI or doest the HTTP adapter handles HTTPS? I think receiver doesnt want a soap envelope. I am sending a text file which has ras edi data and that's what the receiver needs.
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>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>USBANK</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while creating the HTTP client with destination USBANK</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Menaga

Http receiver channel works fine. SM59 gives an error

Hi,
I've set up HTTP receiver communication channel with the following details:
addressing type       : URL address
target host                : cl-test.zzzz.nl
service number        : 20212
path                          : /zz/servlet/runHXML?site=sap&thread=something
authentication data   : use logon for NON sap system.
When i send a message it arrives at the receiver side, and i get "succesfully processed" in the sxmb_moni.
I want to use addressing type HTTP destination instead of URL address so i created an HTTP destination (type G) in SM59 with the same details.
But when i perform the connection test i get an Internal Server Error
(~response_line HTTP/1.1 500 Internal Server Error)
I tried replacing the target hostname with the ip-address, but still the same response.
What can be wrong?
Kr
Robert

Hello Robert,
When you try to test the HTTP destination in SM59, XI send a HTTP Post to the target system but with no payload.
In your case I assume that the Target System cannot process this message and hence triggers a Internal server Error - HTTP 500.
Can you use this HTTP destination and try to test the working scenario end to end. This should work.
Regards,
Bhavesh

HTTP Status Code 200 Received But Error During Response Parsing

Hi Experts,
We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
<?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">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We searched other threads but could not get any solution. Please provide suggestions.
Thank You.
Regards,
Anandan

the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically and as a result , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
We have done the following activities in order to solve this problem....
increase the value of icm/HTTP/max_request_size_KB to 512MB
 icm/wp_roll_timeout to maximum
 HTTP TIMEOUT to 1800 sec
 icm/wp_roll_timeout to maximum
 mpi/total_size_MB to maximum
 mpi/buffer_size to maximum
and then increased the maxthreadcount ,maxcontentlength using config tool...
and also increased the java heap size to maximum....
After doing everything ,the file has been successfully processed....
the problem has been resolved...

HTTP-Receiver: Code page conversion error from UTF-8 to ISO-8859-1

Hello experts,
In one of our interfaces we are using the payload manipulation of the HTTP receiver channel to change the payload code page from UTF-8 to ISO-8859-1. And from time to time we are facing the following error:
u201CCode page conversion error UTF-8 from system code page to code page ISO-8859-1u201D
Iu2019m quite sure that this error occurs because of non-ISO-8859-1 characters in the processed message. And here comes my question:
Is it possible to change the error behaviour of the code page converter, so that the error will be ignored?
Perhaps the converter could replace the disruptive character with e.g. u201C#u201D?
Thank you in advance.
Best regards,
Thomas

Hello.
I'm not 100% sure if this will help, but it's a good Reading material on the subject (:
[How to Work with Character Encodings in Process Integration (NW7.0)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
The part of the XSLT / Java mapping might come in handy in your situation.
you can check for problematic chars in the code.
Good luck,
Imanuel Rahamim.

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

SOAP Receiver Success / HTTP Receiver Error

Hello,
we have to connect to a http server (HTTP with user authentication). I have tried both a HTTP receiver channel as well as a SOAP receiver channel (option "Do Not Use SOAP Envelope").
Connection using the SOAP receiver works without problem. If we switch to plain HTTP receiver (same connection details) we get the following error:
"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
What could the reason for this? Probably related to the ABAP Stack?
Edited by: Florian Guppenberger on Jan 26, 2010 3:12 PM

Hi,
>>>What could the reason for this? Probably related to the ABAP Stack?
check the log on ABAP for RFC dest from SM59
there you might see some more info
BTW
does PI/XI have access to this http sever ? (no firewalls etc?)
Regards,
Michal Krawczyk

ICM_HTTP_CONNECTION_FAILED error on http receive method

Hi,
I am trying to read a XML via http. I have developed a code referencing this blog:
/people/rashid.javed/blog/2007/03/11/cricket-world-cup-http-client-and-simple-transformations
When http receive method is executed it gives me an error.
On executiong of: CALL METHOD client->receive it gives error:
code: 400 message: ICM_HTTP_CONNECTION_FAILED
I treid changing host and buf in code below both to http://www.google.com to rule out the possibility of bad url. Also tried setting time out to 500 in send method. Still no luck.
ICM trace shows following:
Thr 4864] *** WARNING => Connection request from (16/6462/1) to host: http://www.google.com/, service: 80 failed (NIEHOST_UNKNO
How do I solve this error, please give me some tips.
I was looking forum for this issue but was not able to find a solution.
Here is complete code:
DATA: client TYPE REF TO if_http_client.
DATA: host TYPE string.
* DATA: proxyh TYPE string VALUE 'IfYouHave.Proxy.com',
* proxyp TYPE string VALUE '8080'.
DATA: buff TYPE string,
 respd TYPE string.
DATA: subrc TYPE sysubrc.
CALL METHOD cl_http_client=>create
EXPORTING
 host = 'http://www.google.com/ig/api'
* SERVICE =
* proxy_host = proxyh
* proxy_service = proxyp
* SCHEME = SCHEMETYPE_HTTP
* SSL_ID =
* SAP_USERNAME =
* SAP_CLIENT =
IMPORTING
 client = client
EXCEPTIONS
 argument_not_found = 1
 plugin_not_active = 2
 internal_error = 3
 OTHERS = 4
IF sy-subrc <> 0.
WRITE:/ ' cl_http_client=>create, subrc = ', sy-subrc.
EXIT.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
buff = 'GET'.
CALL METHOD client->request->set_header_field
 EXPORTING
 name = '~request_method'
 value = buff.
buff = 'http://www.google.com/ig/api?weather=21218&hl=en'.
cl_http_utility=>set_request_uri( request = client->request
 uri = buff ).
subrc = cl_http_utility=>get_last_error( ).
IF subrc <> 0.
 WRITE: / 'Wrong URI format'.
 EXIT.
ENDIF.
ENDIF.
CALL METHOD client->send
* EXPORTING
* TIMEOUT = CO_TIMEOUT_DEFAULT
EXCEPTIONS
 http_communication_failure = 1
 http_invalid_state = 2
 http_processing_failed = 3
 http_invalid_timeout = 4
 OTHERS = 5
IF sy-subrc <> 0.
CALL METHOD client->get_last_error
 IMPORTING
 code = subrc
 MESSAGE = buff.
WRITE: / 'communication_error( send )',
 / 'code: ', subrc, 'message: ', buff.
EXIT.
ENDIF.
CALL METHOD client->receive
EXCEPTIONS
 http_communication_failure = 1
 http_invalid_state = 2
 http_processing_failed = 3
 OTHERS = 4.
IF sy-subrc <> 0.
CALL METHOD client->get_last_error
 IMPORTING
 code = subrc
 MESSAGE = buff.
FORMAT COLOR COL_BACKGROUND.
WRITE: / 'communication_error( receive )',
 / 'code: ', subrc, 'message: ', buff.
WRITE: / 'communication_error'.
EXIT.
ENDIF.
respd = client->response->get_cdata( ).
WRITE:/ respd.
Thanks in advance,
CD
Edited by: CD on Feb 19, 2009 1:46 PM

Check this link..
[HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED;

HTTP - Receiver - PLAINHTTP_ADAPTER Error

Similar Messages

Maybe you are looking for