You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Preben Asmussen (Jira)" <ji...@apache.org> on 2020/01/22 16:11:00 UTC

[jira] [Commented] (CAMEL-14220) camel-activemq - Setting brokerURL via camel-main issue

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

Preben Asmussen commented on CAMEL-14220:
-----------------------------------------

When upgrading to 3.0.1 from 3.0.0 I found issue in initializing the Activemq FailoverTransport. It will always use localhost:61616.

I think we should reopen this issue.

See gitter [https://gitter.im/apache/apache-camel?at=5e284b963fd0cc7cfe17da8d]

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