You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we encountered a very strange behaviour in our Camel-K integrations. Our body consits of an list with about 10.000 entries and we try to do an parallel split to send them to kafka. In our log we can see, that there are 10 threads, but they are running sequentially. The second thread starts after the first one finishes. We thing that this could be a problem regarding camel-k, because we already have a kind of similar route built with Camel Spring Boot and it's running as intended.
This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!
Hello guys,
we encountered a very strange behaviour in our Camel-K integrations. Our body consits of an list with about 10.000 entries and we try to do an parallel split to send them to kafka. In our log we can see, that there are 10 threads, but they are running sequentially. The second thread starts after the first one finishes. We thing that this could be a problem regarding camel-k, because we already have a kind of similar route built with Camel Spring Boot and it's running as intended.
Here are our used routes:
Is this a known issue or am I doing something wrong?
Best regards,
Danny
The text was updated successfully, but these errors were encountered: