Huge Processing Time in XI

[Former Member]

Hi All,

We have an interface running in production server which is taking huge processing time.

It is a File to IDoc scenario wherein the file size is about 1MB and it gets converted to something between 4-5MB after Content Conversion. Also, this issue does not happen for all the messages. A few of the messages, say 2 out of 10 messages take this huge time to process (from 2 hours u2013 4 hours sometimes) and the rest of them get processed in few minutes (max. 10mins).

I am just confused with this random behavior of this interface. Has anyone come across anything related to this?

Please help with your inputs.

Many Thanks,

Regards,

Lakshmi.

[Former Member · Accepted solution]

Hi,

Please check if for the instances where the interface is taking a huge time to process, any other interface is running simultaneously and taking up the system resources, due to which this particular message is getting delayed.

Also, for file with content conversion, you can consider splitting up the file in the sender communication channel (parameter RecordSets per message) to reduce the message size.

Also, in transaction code SXMB_ADM, Integration Engine Configuration, you can maintain parameter

EO_MSG_SIZE_LIMIT of category TUNING to process large messages in series. This will ensure that large messages are processed in a seperate queue and do not affect the execution of other interfaces.

You can refer to the below link for sizing and performance tunning

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/2016a0b1-1780-2b10-97bd-be3ac62214c7

Regards

[Steven_UM]

We have seen this happening at our system as well ...

The ' randomness' of this might be caused when the JAVA stack nearly runs out of memory and starts doing garbage collections to remedy ... mapping such large files with convent conversions causes alot of JAVA string manipulations which are very memory consuming.

Have a look at your system logs and check whether GC are occuring ... if they do then you might consider throwing in additionaly memory for your JAVA stacks, add more AS or prevent multiple files from being processed at once (assuming this is happening now and causes even more spikes ) ...

Regards,

Steven

[former_member472138]

This has everything for you.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f...

Regards

Pothana

[naveen_chichili]

Hi Lakshmi,

I have faced same problem and solved by increaseing the below parameter .

ICM Parameters: Check your ICM parameters (ex: icm/conn_timeout = 900000. icm/HTTP/max_request_size_KB = 2097152)

Cheers!!!

Naveen.