Error when sending message: 500 Timeout

[Former Member]

while sendin a message in the http to rfc scenario, im gettin this error message "Error when sending message: 500 Timeout".

can any1 throw some light on this.

[Former Member]

Hi venu,

you need to go to RZ10 and there select the profile instance and go with the extended maintance option in the change mode.

there are two ways you can change it:

1. check out note: 824554

TCODE - rz10

icm/server_port_0 = PROT=HTTP,PORT=8010,TIMEOUT=800,PROCTIMEOUT=800

(for 800 seconds)

8010 is my HTTP port so you have to change it:)

2. SXMB_ADM -> configure integration server -> change specific identifiers

runtime parameter:

Parameter HTTP_TIMEOUT

Meaning

Specifies the timeout for http connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.

Personally I only changed the one from the instance profile but the second one should work too

My suggestion is change only PROCTIMEOUT to 600 or 900 but dont change TIMEOUT. Imp thing is u need to restart the XI, then onlychanges will take place.

If these dosent work out go for changing TIMEOUT also. Just set the value for the instance and dont maintain the HTTP_Timeout in the sxmb_adm

Let me know what u have done , if it works

Thanks,

srini

[Former Member]

Hi Venu,

Check this on 500 timeout:

http://help.sap.com/saphelp_nw04s/helpdata/en/a1/7b61d4fa1f11d1a99800a0c9430730/frameset.htm

• Reward points if helpful. *

Regards,

Subhasha Ranjan

[former_member529475]

HI Venu

Check this parameter:

icm/conn_timeout and icm/keep_alive_timeout

(probably you have to increase it).

Did you check michal weblog about timeouts ?

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

Cheers..

Vasu

<i>** Reward Points if found useful **</i>

[Former Member]

Hi venu,

you find that, despite these errors, your ping has been successfully sent to the other site, this most likely means Movable Type simply did not receive back a non-error reply from the recipient server in enough time to conclude the ping was successful.

Try adjusting the PingTimeout directive in mt-config.cgi1.

This setting defaults to 15, so experiment with a higher number. Note that this may increase the time it takes to save a new entry, because Movable Type will wait longer for a response from the recipient server.

If you continue to see these errors even after increasing the PingTimeout, then there may be a problem with the recipient server itself.