HTTP Post Outbound scenario - Error 110 - Timeouts in SMICM Tracefile

Question

HI There
We have a scenario where we do a HTTP post using the HTTP Plain Adapter to a SMS service provider from a message received from a BW system via RFC, It works perfectly in our development system but we cannot get it working in our production system
In SXI_MONITOR the message fails with the error
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Call Adapter
  -->
- <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>
Running a trace in SMICM shows the following in the tracelog
[Thr 4632] IcmConnRollInWP: no need to roll in WP status: ROLLED IN
[Thr 4632] IcmReadFromConn(id=9/140033): request new MPI (0/0)
[Thr 4632] MPI<3018f>19#4 GetOutbuf -1 cb2250 65536 (0) -> 0DE122B0 0
[Thr 4632] NiIRead: hdl 43 recv would block (errno=EAGAIN)
[Thr 4632] NiIPeek: peek for hdl 43 timed out (r; 500ms)
[Thr 4632] NiIRead: raw read for hdl 43 timed out (500ms)
[Thr 4632] IcmReadFromConn: read failed with timeout: 500 -> roll out
[Thr 4632] MPI<3018f>19#5 WriteOOB 00000000 02000000 09000000 01
[Thr 4632] MPI<30190>15#11 ReadOOB 01000000 01000000 2D000000 00 -> 0
[Thr 4632] IcmHandleOOBData: Received data on 1st MPI (seqno: 1, type=1, reason=1): 45/14512/0
[Thr 4632] MPI<3018f>19#10 ReadOOB 01000000 01000000 2D000000 00 -> 0
[Thr 4632] IcmHandleOOBData: Received data on 2nd MPI (seqno: 1, type=1, reason=1): 45/14512/0
[Thr 4632] IcmHandleOOBData: Received context key (type=1, reason=1): 45/14512/0
[Thr 4632] NiWakeupExec: send wakeup signal to 64997 (sock 16992)
[Thr 4632] IcmConnRollOut: connection (id=9/140033) rolled out:
[Thr 4632] CONNECTION (id=9/140033):
    used: 1, type: 1, role: 2, stateful: 0
    NI_HDL: 43, protocol: HTTP(1)
    local host:  200.1.1.100:3405 ()
    remote host: 196.30.220.242:80 ()
    status: READ_RESPONSE
    connect time: 23.07.2008 07:13:10
    WP-status: ROLLED OUT (Context: 9, Role: 2)
              tid: 45, mode: 0, uid: 14512, roll-reason: ICM_ROLL_NETTIMEOUT
With the following 2 lines ir differs from our development system  - this is the point where it goes wrong
[Thr 4632] NiIRead: raw read for hdl 43 timed out (500ms)
[Thr 4632] IcmReadFromConn: read failed with timeout: 500 -> roll out
We have already checked the following between the 2 systems
1. Configuration in Netweaver Administrator is Consistent
2. Communication channel and Mapping is consistent
3. Profile parameters for ICM are consistent
Any ideas as to what this problem could be
Many Thanks

Answer 1

Hi
after you download the html client.
go to view -> source
and enter the present xiusername & pwd which you using and save.
Enter the below details in http client.
Servername : XIServername
Port : 80<instancenumber>
Client : XI server client number
Server : Sender service (business service or busienss system or integration process...when it comes to the HTTP adapter you need to create the business service that business service name you need to enter )
Interface name : outbound interface name
namespace : name for interface.
If you doing Party scenario enter the Party, Agency and Schema details also else optional.
Enter the Input xml data while enter the input data remove the first xml version line and paste the other data.
click on send message.
check the exchange profile set the httpport or not
check these links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
The specified item was not found.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/http%2bto%2brfc%2bsynchronous%2bscenario%2b-%2bfaqs
HTTP to RFC - A Starter Kit
/people/r.eijpe/blog/2006/02/19/xml-dom-processing-in-abap-part-iiia150-xml-dom-within-sap-xi-abap-mapping
Regards,
Suryanarayana