I am testing by using REST Connector to orchestrate the process. My issue lies in the Connector, which sends only one requests to the API at a time. And if Task 1 has messages to send, Task 2 cannot begin its independent sending process until Task 1 is complete. Upon further examination, I’ve discovered that this issue not only impacts the current process but also affects other processes that utilize REST Connect.
For testing purposes, I have set up two simple APIs to receive messages from Camunda. The first API intentionally waits for 10 seconds before completing its task. As you can observe from the image, despite having four messages to send, only one message was actually sent to my API. The Connector is waiting to receive a response from my API before it can proceed to send the second message.
Hi @mark.farkas ,
Thank you for your response. I am using the connectors-bundle image in my local environment.
From my understanding, I should add the configuration as environment variables for the connector container, correct?
Hi @mark.farkas ,
Thank you for your response. I have tested it, and it works. However, I have another question regarding the configuration zeebe.client.worker.threads . If I have two different workflows, with 100 messages on workflow A and 100 messages on workflow B, does this mean that workflow B has to wait for workflow A to complete all its messages before executing? Is that correct?
Could this potentially create dependencies between different workflows?
Hi @Larry ,
The assumption is basically correct. Zeebe will process as many processes parallelly as the value of the zeebe.client.worker.threads property (because it creates as many threads for execution). Let’s assume this value is 32. This means if you have 100 process instances on process definition A, and 100 on process definition B, Zeebe will process 32 of them parallelly, and the rest has to wait, but you cannot tell which 32 will be processed first (can be any combination of process definition A and B).
