Thundercloud12 commented on PR #6845: URL: https://github.com/apache/camel-k/pull/6845#issuecomment-5843435227
# ArkMQ / ActiveMQ Artemis AMQP Verification **Issue:** #5935 – Support ArkMQ in Pipe Binding **Date:** 2026-09-26 ## Objective Verify the AMQP configuration used by the ArkMQ Pipe binding against an ActiveMQ Artemis broker. ## Verification Tested with: * **Camel:** 4.22.1 LTS * **Qpid JMS:** 2.11.0 * **ActiveMQ Artemis:** 2.44.0 * **JDK:** 21 An Artemis broker was started with both AMQP acceptors: * `61616` — multi-protocol (`AMQP`, `CORE`, `MQTT`, etc.) * `5672` — dedicated AMQP Both were tested using: ```text amqp://localhost:<port> ``` with the Camel endpoint: ```text amqp:queue:<destination> ``` ### Results **Port 61616:** SUCCESS Camel connected, created/used the queue, produced a message, and consumed it successfully. **Port 5672:** SUCCESS Identical behavior; AMQP 1.0 connection and message flow worked successfully. ## Configuration For Camel K, the following properties were verified: ```properties quarkus.qpid-jms.url=amqp://<host>:<port> camel.component.amqp.broker-url=amqp://<host>:<port> ``` The Pipe binding can therefore continue using: ```text amqp:queue:<destination> ``` without additional custom connection/bean configuration. ## Conclusion The current ArkMQ binding configuration is compatible with ActiveMQ Artemis AMQP. * `61616` supports AMQP 1.0 despite being a multi-protocol port. * `5672` also works as the dedicated AMQP port. * No changes to the current binding translation are required based on these tests. -- 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]
