[
https://issues.apache.org/jira/browse/ARTEMIS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278359#comment-17278359
]
Justin Bertram commented on ARTEMIS-3094:
-----------------------------------------
It looks to me like everything is working as designed.
The first thing to note is that the documentation you're using is from version
1.0.0 which was released over 5 years ago now. Notice the {{1.0.0}} in the URL.
[This|http://activemq.apache.org/components/artemis/documentation/latest/] is
the documentation you should be using since 2.16.0 is the latest release.
The string {{jms.local.}} doesn't match {{local.mytopic}} so the bridge won't
forward messages sent to that address to the cluster. I'm not sure what to
recommend for a working value as your entire use-case isn't clear.
If you want to follow up please take this issue to the [ActiveMQ user mailing
list|http://activemq.apache.org/contact#mailing]. Jira is typically reserved
for confirmed bugs, feature requests, etc.
> Cluster connection address issue/question
> -----------------------------------------
>
> Key: ARTEMIS-3094
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3094
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.16.0
> Reporter: Scott Ortel
> Priority: Major
>
> I have multiple servers setup as a systemic cluster (ON_DEMAND, max hops =1).
> All works really well. Message consumers on all brokers are getting
> messages.
> However, if I attempt to restrict the messages being sent to the cluster
> using the 'address' cluster connection setting as setAddress("jms.local."),
> JMS topics of the form ("local.mytopic) stop flowing. Maybe this is not the
> intent of the 'address' property or I have misunderstood something.
> I was using the following as a guide:
> [http://activemq.apache.org/components/artemis/documentation/1.0.0/clusters.html]
> Thanks for your help.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
