camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Minh Tran <>
Subject Re: message to remote topic
Date Tue, 19 Jul 2016 10:15:41 GMT

I’ve never used the network: prefix before but you’ll definitely need the rest of what
you’re passing into brokerURL

You definitely need the bean declaration if you want to connect to a remote host.

If you want to connect to both a local and a remote activemq host, just declare 2 beans and
name them appropriately and then use the bean names in the uri.
eg <inOnly uri=“remoteActiveMQ:topic:remoteTopicName”/> or
<inOnly uri=“localActiveMQ:topic:remoteTopicName”/>

> On 19 Jul 2016, at 5:12 AM, lw <> wrote:
> Hello,
> I'm figuring out how to send a message to a topic located on remote host. So
> far, I worked exclusively with local activemq queues. I found several camel
> help pages relevant to the topic and would like to confirm few things here.
> It seems I should be able to connect to a remote activemq in the following
> way:
>    <spring:bean id="activemq"
> class="org.apache.activemq.camel.component.ActiveMQComponent">
>        <spring:property name="brokerURL"
> value="network:tcp://remotehost:61616?trace=false&soTimeout=6000"/>
>    </spring:bean>           
> It seems to me that having "network" in the value is important. Is that true
> or can I omit it?
> If the above looks right, I think I should be able to send an async message
> to remote topic in the following way
> <inOnly uri="activemq:topic:remoteTopicName"/>
> Would th eabove reach the remote topic?
> Also, I'm curious if I could put all info about remote topic and remote
> activemq into the "inOnly" tag, without the bean declaration?
> If anyone had a hands-on experience with the above and has some
> dos-and-donts pointers, I'd very much appreciate the input.
> Thanks a lot.     
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

View raw message