Timeout parameter for RFC Receiver not affecting

[manoj_khavatkopp]

Hello Experts,

I have a SOAP to RFC sync scenario , so the RFC is taking more then 5 mins to execute .Yes i understand that it's not a good idea to increase timeout more then 5 mins but unfortunately considering the business scenario and timeline critical this is the only option i have . So re-designing is not possible at this point.

Below are the things which i have already tried :

1.Set the parameter xiadapter.inbound.timeout.default to 600000

2.Restarted RFC/XI/messaging system.

3.Tried adding syncTimeout to 600000 in RFC channel.

4. Set syncMessageDeliveryTimeoutMsec to 600000.

But whatever changes i see the Parameter in Reliable messaging in monitoring still remains 300000 i.e 5 mins.

Has anyone successfully set this timeout ? i Would consider the system restart as last option . Any other inputs are most welcome.

Br,

Manoj

[manoj_khavatkopp · Accepted solution]

Ok finally looks like its working. I added this syncTimeout parameter in soap channel instead of RFC and keeping external BP in ECC BAPI i made it to wait more then 10 mins, now i can see the parameter value is changed to 60000. but what if i want to test it from RWB why actually the parameter xiadapter.inbound.timeout.default is not affecting as this is the global parameter 😐

Update : ok the global parameter affect takes place only after the complete restart . To Hell with PI ��

Br,

Manoj