MessageExpired because of large amount of data

[Former Member]

Hi Experts, i need some advice for my following scenario.

I have a 50000 data that need to be inserted into SAP R3 HR. I am using BPM when calling the RFC dan using a sync message to get the response from the RFC. However, i think because of the large amount of data, i get the error "MessageExpired" in my monitoring.

After i read some documentation, i find that a sync message has a timeout period (xiadapter.inbound.timeout.default = 180000 [ms] ) . My question is, if the 180000ms is not enough for the RFC to process the whole 50000 data, i can increase the timeout time, am i right? But then, to what maximum value will be the most appropriate for me to set the timeout value so that it will not effect the performance of XI. Anyway, does increasing the timeout value effect anything at all?

Need the advice and inputs from you experts...Thank you so much in advance...

[Former Member · Accepted solution]

Made,

I posted this answer to a similar request a couple of weeks ago

I had a similar issue some time back and used the following three parameters

1. Visual Administrator

SAP XI Adapter: RFC parameter syncMessageDeliveryTimeoutMsec

This parameter is explained in SAP Note 730870 Q14 and SAP Note 791379

2. Alert Configuration

SA_COMM parameter CHECK_FOR_ASYNC_RESPONSE_TIMEOUT

This parameter specifies the maximum time in seconds that can pass between the arrival of the synchronous request message on the Integration Server and the asynchronous response message. If this time period is exceeded, a system error is returned to the caller.

3. Integration Process TimeoutControlStep

My design is such that timeout parameter 3 which is set in the Integration Process will be triggered first. This will give me control to handle the timeout via an SMTP email prior to either of the other timeouts taking effect

Regards,

Mike

[Former Member]

Made,

There is no definitive answer

As with any system tuning it will be specific to your environment and requirements but must cater for all interface scenarios

(1) You could up the timeout value and retest until the message is processed

(2) You could engage SAP with a customer message and ask for a magic value but again this is more subjective and would still require retesting

(3) Is it possible to reduce the message size being processed either from its source or possible within the BPM?

Regards,

Mike

[Former Member]

Thx all for the helps...It solved...

[GabrielSagaya]

As per the documentation

http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd5...

You should increase the timeout from 180000(default) to 240000.

But increasing the timeout value effects anything at all since you include BPM which ver much affect the performance.

[Former Member]

Thk so much guys for all the help. Am i right to say that for my scenario the key issues will be in this parameter: xiadapter.inbound.timeout.default = 180000 [ms] ...

There is no other way (except make it async) that i can do except increasing this value right??