BPM: error at exactly 2500 messages after message split: no coincidence?

[Former Member]

Hi everybody,

we poll a message, split it in BPm and than call a WebService.

We got an error exactly after 2500 messages were processed successful.

Is there a special parameter which influences the BPM?

Thanks a lot

Regards Mario

[Former Member]

Hi,

In SXMB_ADM you can set the time out higher for the sync processing.

Go to Integration Processing in SXMB_ADM and add parameter SA_COMM CHECK_FOR_ASYNC_RESPONSE_TIMEOUT to 120 (seconds). You can also increase the number of parallel processes if you have more waiting now. SA_COMM CHECK_FOR_MAX_SYNC_CALLS from 20 to XX. All depends on your hardware but this helped me from the standard 60 seconds to go to may be 70 in some cases.

Make sure that your calling system does not have a timeout below that you set in XI otherwise yours will go on and finish and your partner may end up sending it twice

when you go for BPM the whole workflow

has to come into action so for example

when your mapping last < 1 sec without bpm

if you do it in a BPM the transformation step

can last 2 seconds + one second mapping...

(that's just an example)

so the workflow gives you many design possibilities

(brigde, error handling) but it can

slow down the process and if you have

thousands of messages the preformance

can be much worse than having the same without BPM

see below links

http://help.sap.com/bp_bpmv130/Documentation/Operation/TuningGuide.pdf

http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap%20excha...

Regards

Chilla..

[Former Member]

There is a SAP node regarding this problem!

Thanks Mario

[Former Member]

Mario,

It would be helpful for us if you can five the SAP Note number...

Regards,

Jai Shankar

[Former Member]

Could you please share the note number ?

Thanks.

[Former Member]

OSS 906472

Happy weekend!

Regards Mario

[former_member431549]

So Mario, are you saying you found the answer in this note ? Because I believe you did. As indicated in the OSS note, T-code SWPA is probably set to a max node of 2500 on your system. Raise the value and see what happens.