You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2020/05/05 13:34:00 UTC

[jira] [Comment Edited] (CAMEL-14643) Configuring brokerurl leads to duplication in camel-activemq and spring-boot

    [ https://issues.apache.org/jira/browse/CAMEL-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099872#comment-17099872 ] 

Claus Ibsen edited comment on CAMEL-14643 at 5/5/20, 1:33 PM:
--------------------------------------------------------------

Update your github project so its easier for us to reproduce please.

And add instructions if needed how to run/test etc


was (Author: davsclaus):
Update your github project so its easier for us to reproduce please.

> 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)