oscerd commented on issue #1514: URL: https://github.com/apache/camel-kafka-connector/issues/1514#issuecomment-6632195898
Sorry this went unanswered. The reconnect after every message happens because Camel's JMS producer sends through Spring's `JmsTemplate`, which needs a caching or pooling connection factory to reuse connections (see https://camel.apache.org/components/next/jms-component.html), and a plain `org.apache.qpid.jms.JmsConnectionFactory` does not pool. In 4.22.x the AMQP sink is camel-jms-amqp-10-sink-kafka-connector, generated from the `jms-amqp-10-sink` Kamelet, which still creates a plain `JmsConnectionFactory`; the same behaviour was reported upstream in https://github.com/apache/camel-kamelets/issues/1936, which was resolved by adding pooled Kamelets for ActiveMQ Artemis only (available here as camel-jms-pooled-apache-artemis-sink-kafka-connector, which uses the Artemis core protocol). If your broker is not Artemis, a pooled AMQP 1.0 Kamelet needs to be requested in apache/camel-kamelets, and camel-kafka-connector picks it up with its next Kamelets catalog update, so closing this her e; for any other problem with the 4.22.x connectors, please open a new issue with the version, configuration and logs. --- _Claude Code on behalf of Andrea Cosentino_ -- 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]
