topic Re: loopCardinality in multi instance subprocess unchecked in Alfresco Archive

loopCardinality in multi instance subprocess unchecked

page80 — Thu, 12 Dec 2013 16:07:13 GMT

I have a multi-instance, non-sequential, subpprocess that has an activiti:collection with (currently) two elements in it.However, when setting multiInstanceLoopCharacteristics, I set the loopCardinality value to 5 (doing what have gleaned to mean a maximum of 5 instances/threads can run concurrently

Re: loopCardinality in multi instance subprocess unchecked

brianok — Thu, 12 Dec 2013 19:37:24 GMT

I'm not a BPMN expert but I thought loopCardinality is meant to "hardcode" the number of times to run the step and is not intended to have anything to do with iterating on collections. Since activiti:collection is an Activiti extension, I would suspect that you are doing something that is unexpected. I'm not sure there is a way to delegate Activiti to only use N threads of the thread pool. There probably is a way to set the overall size of the thread pool, but I don't know what it is.

Re: loopCardinality in multi instance subprocess unchecked

frederikherema1 — Fri, 13 Dec 2013 07:57:48 GMT

The loopCardinality is NOT controlling how many threads are used, is controls EXACLTY how many times the Multi-instance activity will be executed (being either in a parallel execution or sequential). If you use this toghether with an activiti:collection (or loopDataInputRef), you should make sure the collection actually contains 5 (or more) elements.

If you're NOT sure the collection will contain 5 elements, use the completion-condition instead to check the loopCoonter is less than 5 and remove the loopCardinality declaration…