You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/02/03 21:14:00 UTC
[jira] [Resolved] (ARTEMIS-3094) Cluster connection address
issue/question
[ https://issues.apache.org/jira/browse/ARTEMIS-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-3094.
-------------------------------------
Resolution: Not A Bug
> 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)