Return-Path: 
 <activemq-users-return-1479-apmail-geronimo-activemq-users-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org
Received: (qmail 89798 invoked from network); 23 May 2006 03:45:28 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 23 May 2006 03:45:28 -0000
Received: (qmail 81238 invoked by uid 500); 23 May 2006 03:45:28 -0000
Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org
Received: (qmail 81201 invoked by uid 500); 23 May 2006 03:45:27 -0000
Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:activemq-users-help@geronimo.apache.org>
List-Unsubscribe: <mailto:activemq-users-unsubscribe@geronimo.apache.org>
List-Post: <mailto:activemq-users@geronimo.apache.org>
List-Id: <activemq-users.geronimo.apache.org>
Reply-To: activemq-users@geronimo.apache.org
Delivered-To: mailing list activemq-users@geronimo.apache.org
Received: (qmail 81191 invoked by uid 99); 23 May 2006 03:45:27 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 20:45:27 -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, 22 May 2006 20:45:26 -0700
Received: from localhost ([127.0.0.1] helo=talk.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1FiNpR-00069L-Gg
	for activemq-users@geronimo.apache.org; Mon, 22 May 2006 20:45:05 -0700
Message-ID: <4516715.post@talk.nabble.com>
Date: Mon, 22 May 2006 20:45:05 -0700 (PDT)
From: Adrian Co <aco@exist.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Problem with No Subscriber Advisory Topic
In-Reply-To: <4394011.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-Sender: aco@exist.com
X-Nabble-From: Adrian Co <aco@exist.com>
References: <4393897.post@talk.nabble.com> <4394011.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


Hi,

Could you try setting this flag in your destination policy:
sendAdvisoryIfNoConsumers="true"

i.e.

    <destinationPolicy>
      <policyMap><policyEntries>
        
          <policyEntry topic="TEST.FOO" sendAdvisoryIfNoConsumers="true">
            <dispatchPolicy>
              <strictOrderDispatchPolicy />
            </dispatchPolicy>
            <subscriptionRecoveryPolicy>
              <lastImageSubscriptionRecoveryPolicy />
            </subscriptionRecoveryPolicy>
          </policyEntry>

      </policyEntries></policyMap>
    </destinationPolicy>

Let me know if that fixes your problem. :)

Regards,
Adrian Co


himmeric wrote:
> 
> I forgot to mention I'm using a wildcard to setup my
> getConsumerAdvisoryTopic, which seems to work fine.   "topic.>" and I
> receive advisory messages on all subtopics.  
> 
> Since I'm having a problem with the no consumers advisrory I tried that
> with a wildcard "topic.>" and also as individual consumers when the topic
> is created, "topic.subtopicA"  neither seem to receive messages when there
> are no consumers left.
> 
> I'm thinking that the wildcard approach should work for the no consumer
> advisory as well, since the advisory topics appear to be just normal
> topics.
> 
--
View this message in context: http://www.nabble.com/Problem+with+No+Subscriber+Advisory+Topic-t1621608.html#a4516715
Sent from the ActiveMQ - User forum at Nabble.com.