Message getting stuck in XBQO queue - Time limit exceeded

[Former Member]

Hi All,

We have a BPM scenario in our project (on PI 7.0 SP18), where bundle of PEXR2002 Payment IDocs are received as a single flat file. This file is then consumed by the BPM, to split the message into multiple payments using Java Mapping.

However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.

Any pointers to this will be really appreciated.

Thanks & Regards,

ROSIE SASIDHARAN

[Former Member]

This error was due to the Java mapping coding issues - where DOM parsing methods were called multiple times. On optimizing the code, the issue has been resolved.

Thanks,

Rosie Sasidharan.

[Former Member]

H Rosie,

1) Goto SXMB_ADM-> Integration Engine Configuration->Parameter EO_MSG_SIZE_LIMIT->possible values 0 - 2,097,151 (KB)

The parameter EO_MSG_SIZE_LIMIT enables serial processing of messages of a particular size. This applies for messages with the quality of service Exactly Once (EO). If the message is larger than the parameter value, the message is processed in a separate queue.

2) Goto SXMB_ADM-> Integration Engine Configuration->Parameter HTTP_TIMEOUT->possible values n Seconds, where n is a whole number.

The parameter Specifies the timeout for HTTP connections (time between two data packages at line level). This value overrides the system profile parameter icm/server_port_n (for example, icm/server_port_0 : PROT=HTTP, PORT=50044, TIMEOUT=900). If you do not set the parameter HTTP_TIMEOUT or if you set the parameter to 0, then the setting for the system profile parameter is used.

See SAP Note 335162 for sysfail issue....

Hope these will help u....

Regds,

Pinangshuk.

[Former Member]

Hi Rosie,

However, when we get an IDoc file of size greater than 5 MB (more than 500 IDocs), the message gets stuck in XBQO queue and eventually giving a SYSFAIL with the message "Time limit exceeded". Could you please let us know if you have encountered a similar issue and are aware of a possible solution.

This issue arises if the load on the server increases. Either break the incoming file into smaller files (1meg or so) or try increasing the time out parameter in SXMB_ADM -> Integration Engine Configuration.

Worth reading -

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417800%29ID1292465050DB0127930737059291720...

Hope this helps.

Regards,

Neetesh

Edited by: Neetesh Raj on Oct 27, 2009 3:35 PM