Time limit exceeds error in the queue in ECC

[Former Member]

Hi,

We are facing an issue when we try to run our File to Proxy scenario.The message has been split into chunks in PI and is being sent to ECC.The first message being sent is the largest and has hence been prioritized and sent to a dedicated queue.Inspite of increasing the maximum run time for this queue,there is a message stuck in this queue everyday with the error "Time limit exceeded".However,we are able to restart the message and send it in the morning when we come.We are unable to identify the root cause of this issue.

Any help on this would be appreciated.Thanks in advance.

Thanks and Regards,

Induja Ramesh

[Former Member · Accepted solution]

Hi, the best would be to reduce the chunk size as RAJEEV suggest. If you cannot do this, you have to increase the parameter Max. runtime of the desired queues in the QIN scheduler, transaction SMQR.

Check SAP help  http://help.sap.com/saphelp_nwpi71/helpdata/en/3f/425f3c0fdea575e10000000a114084/content.htm

Best regards, Martin

[Former Member · Accepted solution]

Thanks Rajeev and Martin.

The max runtime parameter in transaction smqr has already been increased.However,we will have to increase the keep alive time out parameter and check.We will change it and let you know if it has been successful.Do we have to increase it at both the XI and ECC ends.

Thanks and Regards,

Induja

[Former Member · Accepted solution]

Hi Induja, about the keep alive param of ICM: the Internet Communication Manager is the component of the NetWeaver Application Server that receives and sends Web requests (HTTP, HTTPS, SMTP) (from SAP help), so once the message has entered SMQ2, the ICM has already passed the message to the handler - in your case the queue - and ICM finished processing. So I doubt that increasing the keep alive param will help.

[Former Member · Accepted solution]

in your scenario file to proxy scenario, increasing the keep alive parameter of HTTP service in PI system will be sufficient.

[Former Member · Accepted solution]

Induja Ramesh wrote:
The max runtime parameter in transaction smqr has already been increased.

Can you further increase this param?

What about further reducing the chunk size as RAJEEV suggested?

Is it a custom or SAP delivered proxy? In case of custom proxy, a solution to reduce runtime could be to improve the performance of the ABAP code.

[former_member235717]

Hi,

In my case, the interface is from Proxy to File which is sending a huge file. So sometimes timeout error occurs in our prod system. How can I eliminate this timeout issues?

Thanks!!

[marksmyth]

Hi

What is the value of the PROCTIMEOUT parameter in trx smicm -> Goto -> Parameters -> Display. This should be visible in the icm/server_port_0 parameter.

Also, are there any corresponding dumps in transaction ST22? If yes, post these as they will give more clues as to what is causing the error.

Regards
Mark

[Shabarish_Nair]

another thing you might want to check is if the proxy destinations using a load balanced configuration. It could be that all the messages are hitting a single instance on the target end and thus the delay in processing. this is a common issue in productive landscapes.

[Former Member]

Hi All,

Increasing the keep alive timeout parameter in XI and ECC did not help.Do we have to do a restart after changing these parameters?

Hi Shabarish,

We are not using a load balanced configuration as of now.Please could you let me know what all I will have to check for the same.

Thanks and Regards,

Induja

[Former Member]

pls restart your XI system and see if the keep alive parameter takes effect - hope you would have increased it from 60sec to 600sec.

[Shabarish_Nair]

you might want to talk to your basis team. makes sure all your destinations (Proxy and IDoc) are using load balancer ports and config. Also make sure your RFC adapter is using load balanced configs. this is always a best practice.

[Former Member]

Restarting PI ABAP ICM should be sufficient to activate the new parameters.

If this doesn't help, try to raise ICM trace level to investigate further.

[Former Member]

Hi,

Please set the the keep alive parameter to 180 and proctimeout to 1800 to solve the issue.

Thanks,

Atul.

[Former Member]

in PI system, in SMICM - go to - Services - HTTP, edit the keep alive parameter to a greater value and see if it helps.

moreover, the chunk size of the msg in file sender adapter can be reduced to a slightly smaller value, to reduce the msg size of the msgs flowing through PI.

[Former Member]

Thanks for the reply.

The keep alive timeout parameter is currently set to 60.The problem occurs only in Production,the file is processed without any issues in Quality and Development.

Thanks and Regards,

Induja

[Former Member]

in production system, increase the keep alive parameter to 600. since 60 is a much small value and can lead to time out errors. it happens in prd system because of the load on the system by all the interfaces running on it as and when needed.