HTTP status Code not OK 500 error

[Former Member]

Hi Experts,

Im sending data from XI to receiver proxy, and the synchronous response is sent back to XI.

I get the time out error "HTTP stautus Not ok" 500 error.

This happens only for voluminous message, where as for comparitively smaller messages it runs fine.

I have also adjusted parameters in sxmb_adm, http_timeout to 90000,

The strange thing is when i execute the same payload usig SPROXY, it runs successfully.

request you all to throw some light on this.

Regards,

RK

[former_member307485 · Accepted solution]

Hi Rupash,

Check this parameter: icm/conn_timeout and icm/keep_alive_timeout (probably you have to increase it).

Also check the link:

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Regards,

Divya

[Former Member · Accepted solution]

Hi Divya,

Actually the icm parameter from RZ10 overriden when the http_timeout parameter is specified.

Have you come across any similar situation?

[siddhesh_pathak4 · Accepted solution]

Hello,

Check with SAP Note: 807000 . May be this will help you.

[Former Member]

Thanks to the note number ..problem solved...

Thank you all, u ve been of immense help

Regards,

Rupash

[Former Member]

Hi,

HTTP 500

o Internal error in J2EE

o Check SAP Note 807000 - Http requests are not fully read

after timeout

Regards,

sreenivas

[Former Member]

Hi Rupash,

As rajeev suggested you should it on the ECC side as you say it runs fine with the normal structure.

The real data is causing the stop..

try to increase the http_timout paraneter or as divya suggested on ICM,

go to SCICM, increase keep alive, external bind

Hope it helps.

Regards,

Mohd Tauseef

[Former Member]

Hi Rajeev,

Actually in ECC its been set to 18000(i assume its in secs), so i feel that time should be enoughor is it?..

I have not been authorised to change it as it might effect other apps...

besides this is actually testing being done in quality with real data.

Could you pls advice?

Regards,

RK

[Former Member]

Hi,

Set this HTTP_Timeout parameter in your R/3 system also by transaction SXMB_ADM and then re-run your scenario.

Regards,

Rajeev Gupta