Multiple insance of same transaction (asynchronous mode)

[former_member331439]

Hello

I created a structured service composed by:

- a master transaction executed every 10 minutes which runs several instances (30) of a slave transaction with Asynchronous mode

- a slave transaction with duration between 1 minute and 3 minutes.

I found that

- master transaction complete its task in 10 seconds and runs all 30 instances of slave transactions (asynchronous)

- 18 slave transactions start at once

- 12 slave transactions remain in pendig status till first group finishes

Have you ever found this behaviour?

Is this 18 a fixed limit or a MII parameter? Where could I change it?

Thanks a lot

Regards

Fabio

ps: MII 12.2, netweaver 7.3

[raphael_dasilva · Accepted solution]

Hello Fabio,

Transactions launched asynchronously are handled by MII via JMS and EJB.

You may be able to adapt the behavior in such execution, but it may affect directly the system performance.

I suggest you to check section 'Transactions stuck in PENDING state' of MII handbook.

http://wiki.scn.sap.com/wiki/download/attachments/15603/SAP+MII+Handbook.pdf

Please keep in mind that performance tests are necessary if you modify those values.

Hope it helps !

Please let us know the results.

Best regards,

Raphael

[former_member331439 · Accepted solution]

Hello

I read the article and it was very helpful.

Before to chage MII parameters, I would prefer to change the software inserting a part of code where I check if there are any pending transaction.

Is there any service call useful for this? I tryed some calls from

but none seems the right.

Do you have any idea?

Thanks a lot

Regatrds

[Former Member · Accepted solution]

Hi Raphael,

this parameters are part of Salvatores performance settings:

http://scn.sap.com/docs/DOC-1834

(page 21)

so fabio should do the settings and should be good to go.

Cheers,
Matt

P.S. Obviously I was wrong with my guess. But this setting is also limited to 30 which fits to what fabio is seing.

[former_member331439 · Accepted solution]

Hi Matthias

I'm using a Windows server 2008 R2 with 8GB of RAM an 2 application servers

I'll change soon PercentageOfParallelismAllowed from 30 to 50.

Do you think that I can increase also ExecutorPoolMaxSize? or is better to change other settings (example: to adapt all tags described in page 21 of document suggested by you)?

Thanks a lot

Regards

Fabio

[former_member193328]

Hi Fabio

I think the number of parallel async transactions would depend on either the number of parallel MDB threads allowed for the MDB running the async transaction or the number of cores on our server.

However 18 cores sounds a bit odd to me so it might be the first one.

Regards

Partha

[Former Member]

Looks like you hit some resource limitation, such as thread pool limit etc.

If asynchronous transactions are triggered via JMS then it is quite obvoius. The default limit for the NotificationQueueThreadThreashold is 30 and NotificationQueueMaxThreads, which is 3. See my answer based on Salvatores "MII Performance Doc"