Time Limit Exceeded while executing Proxy Program

[former_member204873]

Hi all,

we are frequently facing Time Limit Exceeded problem in R/3 system while exceuting proxy program for large payloads (appx 5-7 MB). Sometimes we are able to successfully restart the message and sometimes we have to delete these messages. How can we resolve this issue.

Thanks,

Mayank

[turmoll · Accepted solution]

It seems to me that your program is reaching max runtime of you work process (RZ11: rdisp/max_wprun_time) ... have you tried to run it in background via SA38?

/Jakub

[Former Member]

Hi Mayank,

Can you try putting the statement sy-batch = 1 in the beginning of proxy code.

It should solve the problem.

However, you might have to suppress the checkman warning.

Regards,

Vikas

[Shabarish_Nair]

try increasing the timeout parameter;

SXMB_ADM -> Integration engine -> Category: RUNTIME->HTTP_TIMEOUT

[Former Member]

Also check the default timeout for HTTP connections between the SAP systems. By default, this is 60 seconds, so when the timeout occurs by then, this could be the reason. It could be a problem detecting it, because this timeout sometimes is not propagated to the work process. So in SM50 the process keeps running, but in fact the communication is already interrupted. Hope that helps you.

Regards,

Jörg

[former_member204873]

hi Joerg,

we are getting this error in inbound queue in R/3 system, also this is a async call, so no chance of any communication interruption b/w SAP systems. From PI system, message is succeccfully passed to R/3 system & Time Limit Exceeded is coming in R/3 system inboud queue (SMQ2). Is it poosible that timeout will happen within R/3 system.

Thanks,

Mayank

[former_member181962]

Hi Mayank,

To isolate the issue , whether the problem is in XI side or R/3 side, you can try the following.

1) test the proxy from sproxy itself (Provide all the input information in the test tool).

2) Check if the user id that is used for communication from XI-R/3 is Background type or not.

Regards,

ravi kanth

[turmoll]

checm SMQR, if your queue has mode "D" (dialog), then your processing is reaching max runtime for work process ...

set mode to "B" - background

/Jakub

[turmoll]

how to send message into an appropriate queue ("B" not "D") check this weblog: [How to prioritize messages in XI|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2826] [original link is broken] [original link is broken] [original link is broken];

/Jakub

[Former Member]

Hi,

Is it a Synchronous scenario????

Try using commit work. statement inside your proxy (inside loop if exists). This shud reset the timer.

Hope this helps.

Regards,

Siddhesh S.Tawate

[former_member204873]

hi Siddhesh

Actually it's a async scenario.

Mayank

[Former Member]

In that case timeout is in proxy side.... i guess commit work should serve your purpose.