Return-Path: 
 <users-return-38569-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-users-archive@www.apache.org
Delivered-To: apmail-activemq-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4D598109BA
	for <apmail-activemq-users-archive@www.apache.org>;
 Fri, 21 Mar 2014 03:17:06 +0000 (UTC)
Received: (qmail 13809 invoked by uid 500); 21 Mar 2014 03:17:05 -0000
Delivered-To: apmail-activemq-users-archive@activemq.apache.org
Received: (qmail 13530 invoked by uid 500); 21 Mar 2014 03:17:05 -0000
Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@activemq.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@activemq.apache.org>
List-Post: <mailto:users@activemq.apache.org>
List-Id: <users.activemq.apache.org>
Reply-To: users@activemq.apache.org
Delivered-To: mailing list users@activemq.apache.org
Received: (qmail 13521 invoked by uid 99); 21 Mar 2014 03:17:04 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 03:17:04 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Received: from [68.178.252.108] (HELO
 p3plsmtpa11-07.prod.phx3.secureserver.net) (68.178.252.108)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Mar 2014 03:16:57 +0000
Received: from [127.0.0.1] ([117.96.2.3])
	by p3plsmtpa11-07.prod.phx3.secureserver.net with
	id g3GW1n00E03tkGt013GZSJ; Thu, 20 Mar 2014 20:16:35 -0700
Message-ID: <532BAF0D.4030304@mobigraph.co>
Date: Fri, 21 Mar 2014 08:46:29 +0530
From: Netlancer <netlancer@mobigraph.co>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Message forwarding on two brokers not working for MQTT
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi ,

I have setup two brokers A(sender) and B(receiver). both the brokers 
have been configured with transport connector for mqtt protocol. only 
broker A has been setup for network connector.AdvisorySupport is enabled.

I have 2 clients ( producer) connecting to broker A and consumer 
connecting to Broker B. The topic is hierarchical in nature ( c.d ) . 
since i am using mqtt protocol, both producer and consumer uses the 
topic format  ( c/d)

Scenario 1
when  broker A is configured with empty dynamicallyIncludedDestination, 
the consumer in broker B is able to get the message.

when broker A is configured with dynamicallyIncludedDestination as "c.*" 
or "c.>" , the consumer in broker B is not able to get any message. The 
message is never forwarded from broker A to B.

broker A configuration:
         <networkConnectors>
           <networkConnector name="brokerA" 
uri="static:(tcp://localhost:61617)" userName="brokerAusr">
             <dynamicallyIncludedDestinations>
                 <topic physicalName="C1/#"/> or  <topic 
physicalName="C1.*"/> or <topic physicalName="C1.> "/>
             </dynamicallyIncludedDestinations>
           </networkConnector>
         </networkConnectors>

I am using 5.10-SNAPSHOT.

Please, can you let me know if there is anything wrong in the way i have 
configured.

Thanks,
nl