Return-Path: 
 <activemq-dev-return-1929-apmail-geronimo-activemq-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org
Received: (qmail 67165 invoked from network); 17 Jul 2006 20:18:27 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 17 Jul 2006 20:18:27 -0000
Received: (qmail 25809 invoked by uid 500); 17 Jul 2006 20:18:27 -0000
Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org
Received: (qmail 25703 invoked by uid 500); 17 Jul 2006 20:18:26 -0000
Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-dev-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-dev@geronimo.apache.org>
List-Id: <activemq-dev.geronimo.apache.org>
Reply-To: activemq-dev@geronimo.apache.org
Delivered-To: mailing list activemq-dev@geronimo.apache.org
Received: (qmail 25694 invoked by uid 99); 17 Jul 2006 20:18:26 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 13:18:26 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 13:18:25 -0700
Received: from [72.21.53.38] (helo=jubjub.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1G2ZXZ-0000LQ-Hq
	for activemq-dev@geronimo.apache.org; Mon, 17 Jul 2006 13:18:05 -0700
Message-ID: <5367679.post@talk.nabble.com>
Date: Mon, 17 Jul 2006 13:18:05 -0700 (PDT)
From: bmadigan <bmadigan@orbitz.com>
To: activemq-dev@geronimo.apache.org
Subject: Re: Virtual Topics (was Re: Failover topic subscribers)
In-Reply-To: <ec6e67fd0607140359h7c75d86atd873d0cdeafd5c44@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-Sender: bmadigan@orbitz.com
X-Nabble-From: bmadigan <bmadigan@orbitz.com>
References: <ec6e67fd0607140307k637ba13fo89547ab36fb4976b@mail.gmail.com>
 <ec6e67fd0607140359h7c75d86atd873d0cdeafd5c44@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


I added logging to AbstractRegion and the virtual topics broker to see what
destinations are created when a consumer connects. 

INFO  ConsumerGroupsBroker - Adding Consumer for Destination:
topic://ActiveMQ.Advisory.TempQueue,topic://ActiveMQ.Advisory.TempTopic
INFO  AbstractRegion  - Adding consumer:
ID:photon.duncllc.com-60318-1153164652757-1:0:-1:1

When I add a consumer, I'm not sure why it's destination is a temp advisory
topic. I expect to see the destination that the consumer is listening on:
 <property name="destination" value="ActiveMQ.Virtual.TESTGROUP1.TEST"/>

???
I just noticed that the last 3 replies were to myself, so you were probably
not notified.
-- 
View this message in context: http://www.nabble.com/Re%3A-Virtual-Topics-%28was-Re%3A-Failover-topic-subscribers%29-tf1942508.html#a5367679
Sent from the ActiveMQ - Dev forum at Nabble.com.