[
https://issues.apache.org/jira/browse/CAMEL-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021828#comment-17021828
]
Preben Asmussen edited comment on CAMEL-14220 at 1/23/20 7:38 AM:
------------------------------------------------------------------
Sure. I created the project here [https://github.com/pax95/failover-test]
When running the project the failover task will try to connect to localhost
(I see the same behaviour on 3.1.0-SNAPSHOT)
{code:java}
2020-01-23 08:17:32.352 WARN 8463 --- [ActiveMQ Task-1]
o.a.a.t.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 10 attempt(s) continuing to retry.{code}
If you change the camel version to 3.0.0 you should see the expected behaviour
{code:java}
2020-01-23 08:24:20.043 WARN 10019 --- [ActiveMQ Task-1]
o.a.a.t.failover.FailoverTransport : Failed to connect to [ssl://foo:61617,
ssl://bar:61617] after: 10 attempt(s) continuing to retry.{code}
It seems that the FailoverTransport get intialized twice and the default
localhost get's added the second time.
I'm aware of that camel also has a camel.component.activemq.broker-u-r-l, but
when using SB it should still work with the spring configuration property i
would guess
was (Author: preben):
Sure. I created the project here [https://github.com/pax95/failover-test]
When running the project the failover task will try to connect to localhost
{code:java}
2020-01-23 08:17:32.352 WARN 8463 --- [ActiveMQ Task-1]
o.a.a.t.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 10 attempt(s) continuing to retry.{code}
If you change the camel version to 3.0.0 you should see the expected behaviour
{code:java}
2020-01-23 08:24:20.043 WARN 10019 --- [ActiveMQ Task-1]
o.a.a.t.failover.FailoverTransport : Failed to connect to [ssl://foo:61617,
ssl://bar:61617] after: 10 attempt(s) continuing to retry.{code}
It seems that the FailoverTransport get intialized twice and the default
localhost get's added the second time.
I'm aware of that camel also has a camel.component.activemq.broker-u-r-l, but
when using SB it should still work with the spring configuration property i
would guess
> camel-activemq - Setting brokerURL via camel-main issue
> -------------------------------------------------------
>
> Key: CAMEL-14220
> URL: https://issues.apache.org/jira/browse/CAMEL-14220
> Project: Camel
> Issue Type: Bug
> Components: camel-activemq
> Affects Versions: 3.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.0.1, 3.1.0
>
>
> It triggers a lazy create connection factory that uses localhost:61616 and
> sets it due camel-main can detect singleton instanses from registry and auto
> configure them. But sadly activemq uses this lazy create convention in getter
> (legacy from Camel 1.x days)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
