Batch requests to camunda

Camunda 7 Topics
1

Hi,

I have a Camunda workflow that is getting a batch request from my other Java MicroService, this batch request contains about 40 individual requests

But the issue is that up until 20 requests the flow is getting triggered and is successful but after 20 requests it shows in progress only

Is there any limit that I need to change for this? or somewhere in particular I can look?

Thanks!!

2

Hi @ThomasShelby,

Can you provide additional details? What exactly do you mean by batch request? Which API are you using to place the request? Can you share a model and code?

3

Hi @StephanHaarmann ,

Sure,

1)Batch request means that a particular bulk request that has multiple individual requests inside it, each triggering the same Camunda WF
.
2)I am using the Camunda “/start” Url to trigger the WF from my Java MS, and this does not give any issue, the issue presents when the request threshold crosses 20 requests , for instance if the batch requests have 40 requests , it will process20 requests and other requests will be in “In Progress” state only.

  1. I am using Camunda 7 community version, camunda versoin is 7.14 and wildfly is 20.0.1.

4)core-threads count=“10”/
queue-length count=“40”/
max-threads count=“40”/
I have also changed these above values like queue length(queue-length count=“40”/) from 20 to 40, but still it is not going above 20 requests.

  1. And one additional information I wanted, is, is there any URL i can run and check the queue status for this camunda WF, so that I can check number of requests getting stuck and pass.
    Somewhere along the lines of this URL:
    http://serverip:8080/engine-rest/history/process-instance?unfinished=true
    But to check for the whole batch request.

I am also sharing the WF that is being triggered.
NewRequestWorkflow.bpmn (38.5 KB)

4

Your process does not include any transaction boundaries.
Is it necessary that the process is executed synchronously?
If not, have you tried adding an “async before” the start event?

5

I haven’t tried adding async before, will it affect the number of requests recieved and processed?

6

It will affect the processing.
Async before introduces a transaction boundary before the element.
This means the job is written to the database and later picked up by the job executor.
This is strongly recommended:

7

Oh ok, thanks!