Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Subject: Re: Issue with ActiveMQ message replication
To: dev@activemq.apache.org
References: <A72733A73C26FD49ABEF03A8BD062BAA011B9B1264@othydxg20.opentext.net>
From: Matt Pavlovich <mattrpav@gmail.com>
Message-ID: <ba630052-6874-c757-7956-44d2fa7785db@gmail.com>
Date: Wed, 25 Jan 2017 16:34:29 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0)
 Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <A72733A73C26FD49ABEF03A8BD062BAA011B9B1264@othydxg20.opentext.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
archived-at: Wed, 25 Jan 2017 22:34:42 -0000

Hi Dignesh-

Yes, Topics deliver messages to each node over a configured Network 
Connector in ActiveMQ 5.x. You also have the ability to configure which 
topics are delivered to which nodes.

Virtual Topics are also a big help there as they separate the production 
from the consumption and you can do some really fun things with moving 
the messages between brokers in a clean way.

-Matt

On 1/24/17 12:56 AM, Dignesh Goyal wrote:
>
> 1. we do have a requirement of jms messages raised to be processed by each node in a cluster - Looks like topic does this by design. Is there any documentation on how to configure this.
>
> 2. We also want some of the destinations to be not to processed by all the nodes.- Is there any way via configuration to achieve this using Topic
>