https-request: communication_error ( receive ) 110

[Former Member]

Good evening,

we are receiving xml-Data through https-request in our programme on the developement server (T01), everything is fine. Now I ran the programme on the productive server (P01) and I got this error:

communication_error( receive )

code: 110 message:

Corresponding messages on the ICM Monitor P01:

[Thr 3664] *** ERROR => illegal chunk len character: 32 [http_plg.c 6274]

[Thr 3664] *** ERROR => IcmPlAllocBuf: MpiGetOutbuf failed (rc = 7) [icxxplugin.c 1168]

[Thr 3664] *** ERROR => PlugInStopConn: alloc failed(32768) [http_plg.c 1629]

[Thr 3664] *** ERROR => IcmConnClose: PlugInStopConn failed (rc=-701) [icxxconn.c 2919]

Here is what I already checked:

- http request handler is installed properly on P01

- SM59 on P01 returns status code 200, so a https connection to the server I want to reach is possible (although I am not using sm59 in the programme but the URL directly)

- another programme, which also uses the https-request, is returning xml-data on P01 properly, therefore a connection over https is possible in general

- Settings of ICM are the same on P01 and T01

- Certificates in STRUST are the same on P01 and T01

- Instance profile parameters on both servers are the same

Is there anything more to set that I forgot? Is it possible that there is a timout problem on P01 and not on T01, altough T01 has the same settings? Thanks for your suggestions.

Best regards,

Michael

[vincentlim826]

Hi,

What is your P01's kernel/ICM patch level ?

Can you check SAP note 698017 that talks about "illegal chunk len character" ?

Regards,

Vincent

[Former Member]

Vincent,

thank you for your reply. ICM's kernel is patch number 172.

Best regards,

Michael

[vincentlim826]

Mike,

then please apply to latest patch.

Regards,

Vincent

[Former Member]

Vincent,

you are right, but the development system T01 is ICM patch number 77 and the http-request is done without errors. Could there be any other reason for the error on P01?

Best regards,

Michael

[vincentlim826]

Hi Mike,

you got to try it in latest patch, because the behaviour of this error is very much on ICM. As I see, this error can be reproduce on demand, so it should not be difficult for you to test it out with latest ICM patch.

Vincent