[
https://issues.apache.org/jira/browse/CAMEL-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099838#comment-17099838
]
Preben Asmussen commented on CAMEL-14643:
-----------------------------------------
[~davsclaus] Just upgraded to 3.2.0 and SB 2.2.6.RELEASE on the app.
It seems that the allow-auto-wired-connection-factory set to true doesn't work
on 3.2.0 as it did on 3.1.0.
Now SB picks up the right CF (seen on the actuator endpoint), but Camel sticks
to the default 'localhost:61616' ->
Failed to connect to [tcp://localhost:61616]
Some other changes on 3.2 might have changed to affect the behaviour.
The effect can be seen on the example project by upgrading Camel and SB.
> Configuring brokerurl leads to duplication in camel-activemq and spring-boot
> -----------------------------------------------------------------------------
>
> Key: CAMEL-14643
> URL: https://issues.apache.org/jira/browse/CAMEL-14643
> Project: Camel
> Issue Type: Bug
> Components: camel-activemq, camel-spring-boot
> Affects Versions: 3.0.1, 3.1.0
> Reporter: Preben Asmussen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 3.2.0
>
>
> When upgrading from camel 3.0.0 to 3.x.x the spring.activemq.broker-url is no
> longer used when configuring the camel-activemq component.
> It seems that you now have to specify both the spring property (for the SB
> health check to work) and the camel.componnt.activemq.broker-u-r-l for the
> component to work when picking up configuration properties.
> There is an example here [https://github.com/pax95/failover-test]
> when you omit the camel.component.activemq.broker-u-r-l the component picks
> up the default localhost broker and not the spring boot one specified by
> spring.activemq.broker-url
> Maybe there there are some SB bean conditionals missing ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
