Bad http request - Received HTTP response code 400

[alejandro_gmez]

Hi all again:

I'm trying to connect to my XI server using en RFC from my SAP R/3 system.

I've configured my XI Integration Builder (configuration and design).

For test, I'm using SE37. After it, I obtain the next error (obtained from one of the RFC trace files):

**************************************************************************************************************************

RfcAbort called by external program ...

handle = 1

text = call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 400 : bad http request

[1] < accepted > REG <ac: 2> > FLUSH (READ) (15752906)

UUID: send_rfcuuid 942F17CB-EE70-2246-8BC8-07DD3E8FF99F

[1] < accepted > REG <ac: 3> > WRITE (15752906)

000000 | 01010008 01020101 01010000 01010103 |................

000010 | 00040000 020B0103 0106000B 04010002 |................

000020 | 01000200 00002301 06000700 0D31302E |......#......10.

000030 | 3133372E 37332E31 30340007 00110001 |137.73.104......

000040 | 52001100 12000436 34302000 12001300 |R......640 .....

000050 | 04343644 20001300 08000978 69647365 |.46D ......xidse

000060 | 72766572 00080006 000E5A4E 54535F53 |rver......ZNTS_S

000070 | 45415243 485F5849 00060514 0010942F |EARCH_XI......./

000080 | 17CBEE70 22468BC8 07DD3E8F F99F0514 |...p"F....>.....

000090 | 04030012 5246435F 45585445 524E414C |....RFC_EXTERNAL

0000a0 | 5F41424F 52540403 0402007F 63616C6C |_ABORT......call

0000b0 | 20746F20 6D657373 6167696E 67207379 | to messaging sy

0000c0 | 7374656D 20666169 6C65643A 20636F6D |stem failed: com

0000d0 | 2E736170 2E616969 2E61662E 72612E6D |.sap.aii.af.ra.m

0000e0 | 732E6170 692E4465 6C697665 72794578 |s.api.DeliveryEx

0000f0 | 63657074 696F6E3A 20526563 65697665 |ception: Receive

000100 | 64204854 54502072 6573706F 6E736520 |d HTTP response

000110 | 636F6465 20343030 203A2062 61642068 |code 400 : bad h

000120 | 74747020 72657175 65737404 02FFFF00 |ttp request.....

000130 | 00FFFF00 00000000 00000000 00000000 |................

CPIC native call CMSEND [1] convid: 15752906 09:55:53,984

CPIC native call CMSEND [1] convid: 15752906 09:55:53,984

[1] < accepted > REG <ac: 4> > FLUSH(WRITE) (15752906)

CPIC native call CMDEAL [1] convid: 15752906 09:55:53,984

CPIC native call CMDEAL [1] convid: 15752906 09:55:54,000

[1] < accepted > REG <ac: 5> > FLUSH(WRITE) (15752906)

[1] < accepted > REG <ac: 6> > ABORT (15752906)

CPIC native call coxabort [1] convid: 15752906 09:55:54,000

CPIC native call coxabort [1] convid: 15752906 09:55:54,000

[1] < accepted > REG <ac: 7> > CLOSE (15752906)

CPIC native call coxclose [1] convid: 15752906 09:55:54,000

CPIC native call coxclose [1] convid: 15752906 09:55:54,000

[1] < accepted > REG <ac: 8> > FREE (15752906)

<* RfcAbort *>

**************************************************************************************************************************

Thanks to all in advance, sorry my bad prior post and excuse my poor English,

Alejandro Gomez.

[Former Member]

hi

Error: HTTP 400- Bad Request- ICM_HTTP_CONNECTION_FAILED

Description: The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

Possible Tips: May be because of huge message flow. Related SAP Notes-824554, 906435, 783515, 910649, 706563 If it is because of Queue problems have a look into SMQ2 and then go thru this blog- How to Re-Process failed XI Messages Automatically .

note:reward points if solution found helpfull.....

regards

chandrakanth.k

[Former Member]

Hi,

In HTTP status code list the 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.

If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.

HTTP 400 stands for Bad Request

This code indicates that the server could not understand the client's request, or found it to be incorrect in some way.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

for more details on HTTP codes you may follow these links

http://www.web-cache.com/Writings/http-status-codes.html

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm

Thanks

Vikranth