alexkazan87 commented on PR #7454: URL: https://github.com/apache/camel/pull/7454#issuecomment-1109646843
> @alexkazan87 @davsclaus I also add a for concurrency transactions in multithreads. Since the kafka producer does not support multi transactions on a single producer [KAFKA-6278](https://issues.apache.org/jira/browse/KAFKA-6278), I think it should use `seda` and make sure `concurrentConsumers` is **1** and in `kafka` producer with `synchronous=true`. just like > > ``` > from("seda:concurrentConsumers=1") > .to("kafka:" + TOPIC_CONCURRENCY_TRANSACTION + "?requestRequiredAcks=-1&synchronous=true" > + "&additional-properties[transactional.id]=5678" > + "&additional-properties[enable.idempotence]=true" > + "&additional-properties[retries]=5"); > ``` > > can we make this information in our document? or is it not enough? You can hide seda functionality when Kafka transaction is set. I think seda can solve the concurrent issue but I am not aware of this implementation. My reference for this would be something like: public static <T> Future<T> wrap(Callable<T> callable) { .... return task; } from https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/transaction/arjunacore/BaseTransaction.java. We need something similar. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
