cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP Client : Code 110 reason

Former Member
0 Kudos

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

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

We got this code 110 HTTP error after we upgraded XI 3.0 to PI 7.1. The SAP Cryptolib was not installed on the new machine.

For this reason, outgoing HTTPS connections did not work.

After installingt the Cryptoblib, the issue was solved.

CSY

Former Member
0 Kudos

Tirumal,

Is this problem resolved? If yes how it got resolved?

I have the same situation.

Thanks

kishor

Former Member
0 Kudos

Hi Tirumal / Kishore,

does it got resolved?? I am facing similar problem now?? It would be great if you can share your experience.

former_member183909
Active Participant
0 Kudos

Did you ever fix this.? As I also get the same error

Former Member
0 Kudos

Hi Tirumal,

HTTPS might not be enabled in the integration server, only HTTP usualy is enabled. So, enable the HTTPS and it should be OK.

Also check the header details in the SMICM log file. This is not an XI issue its the message from the receiving system.

To enable the HTTPS in IS, check this link

http://help.sap.com/saphelp_nw04/helpdata/en/69/b0bbd6dde71141bee8806586144796/frameset.htm

Regards,

abhy

Former Member
0 Kudos

Abhy -

Its enabled and active on the ABAP Stack but not on Java Stack.

Should it be enabled on the JAVA Stack too?

Thanks,

Tirumal

Former Member
0 Kudos

hi,

In the HTTP Receiver adapter for the Service number i have given the HTTPS port instead of HTTP port since its a HTTPS URL.

This time i get a HTTP Client 400 reason, ICM_HTTP_CONNECTION_FAILED error.

Thanks,

Tirumal

moorthy
Active Contributor
0 Kudos

Hi Tirumal,

Have a look into this thread~

If it solves, please close the thread

Hope this helps,

Regards,

Moorthy

Former Member
0 Kudos

Moorthy -

I am not using Proxy in my scenario but a IDOC ->XI -> HTTP Receiver.

Should i still need to create Business System?

Regards,

Tirumal

moorthy
Active Contributor
0 Kudos

<i>Should i still need to create Business System?</i>

Business System/Service is required if you want to do any Integration Scenario in XI. Irrespective of the Sender/Receiver type.

Thanks,

Moorthy

Former Member
0 Kudos

Moorthy -

I still get the same error. ICM_HTTP_CONNECTION_FAILED.

I have a HTTP Receiver with HTTPS as URL and configured the port to be 443 since its outbound.

1. Do i have to have RFC destination to the outbound HTTP?

2. I checked the SXMB_ADM and i have the http://host:port/sap/xi/engine?type=entry

3. I checked the RWB->Message monitoring, its showing the Error category as PLAINHTTP_ADAPTER and error code as ATTRIBUTE_CLIENT

What else should i configure?

Thanks,

Tirumal

moorthy
Active Contributor
0 Kudos

CHeck this thread-

Thanks,

Moorthy

Former Member
0 Kudos

Moorthy -

I tried with SOAP adapter giving the complete path.

SXMB shows successful. Do not know if the vendor has received it or not.

Doesn't show any error though.

thanks,

Tirumal

Former Member
0 Kudos

Hi Tirumal,

I have the same issue with 'HTTP Client code 110 reason'. Did you finally manage to get it resolved? I am guessing the SOAP solution was not correct as it was a http service and not a web service. Any advice? Thanks.

JoelTrinidade
Active Contributor
0 Kudos

Hi Tirumal,

you were going correct man ...

The 400 error that you are getting can be because of :

  1. The verb used in the request is invalid.

  2. The requested URL is invalid.

  3. The requested header name is invalid.

  4. The requested hostname is invalid.

  5. The request contains an invalid carriage return and/or line feed as a terminator.

  6. The request contains an invalid content length header or invalid entity chunk length.

  7. The cumulative length of the headers in the request is longer than the maximum allowed.

  8. The header field in the request is too long.

  9. The request header is too long.

Check on these lines and see if your problem is solved.

Rgds

joel

markangelo_dihiansan
Active Contributor
0 Kudos

Hi,

Since you are using SOAP now, please check in the Adapter Engine if the message status was set to DLVD. This is the only way to check if the message reached your destination.

As for the other problem:

Would you be able to provide the parameters (type G) of your RFC destination?

Hope this helps,

Former Member
0 Kudos

hi,

Any tips why i am getting this error.

Also how would i test if the message is being received by the receiver.

Let me know if anyone has idea.

Thanks,

Tirumal