[
https://issues.apache.org/jira/browse/CAMEL-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751769#comment-17751769
]
Claus Ibsen commented on CAMEL-19721:
-------------------------------------
This also makes it possible to run camel-jbang with camel-activemq with Camel 4
{code}
~/Downloads ❯ camel run test.camel.yaml
2023-08-07 20:11:29.812 INFO 59570 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 4.0.0-SNAPSHOT is
starting
2023-08-07 20:11:29.925 INFO 59570 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.5 with PID 59570. Started
by davsclaus in /Users/davsclaus/Downloads
2023-08-07 20:11:30.588 INFO 59570 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 20:11:30.681 INFO 59570 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 4.0.0-SNAPSHOT (test) is
starting
2023-08-07 20:11:30.811 INFO 59570 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 20:11:31.025 WARN 59570 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 1 attempt(s) with Connection refused, continuing
to retry.
2023-08-07 20:11:36.184 WARN 59570 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 10 attempt(s) with Connection refused,
continuing to retry.
{code}
The output above start up but since I dont have a local ActiveMQ 5.x running it
fails to connect.
Without this PR then you will get class loader errors.
> camel-activemq - ActiveMQ component should use jakarta based connection pool
> ----------------------------------------------------------------------------
>
> Key: CAMEL-19721
> URL: https://issues.apache.org/jira/browse/CAMEL-19721
> Project: Camel
> Issue Type: Improvement
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.0.0
>
>
> The old code is using activemq-pool which is still javax JMS based so does
> not work with Jakarta and Camel v4.
> We should change the code to use a jakarat JMS pool like Artemis uses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
