Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27662790.post@talk.nabble.com>
Date: Fri, 19 Feb 2010 18:02:22 -0800 (PST)
From: Wxman <Mark.Fenbers@noaa.gov>
To: users@activemq.apache.org
Subject: Re: Persistence not working
In-Reply-To: <27661812.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <27660206.post@talk.nabble.com>
 <7b3355cb1002191401g397380ecx134481566c65c933@mail.gmail.com>
 <27661237.post@talk.nabble.com>
 <7b3355cb1002191508q71a27af0x2ad617b798c5c3b1@mail.gmail.com>
 <27661812.post@talk.nabble.com>


Wxman wrote:
> 
> But, looking at my code, it creates durable subscriptions to topics in my
> *consumer* code.  There is no reference to durable messages in the
> producer code.  So, am I leaving something out?  (I must be, because my
> app doesn't seem to behave in the way you describe Durable Subscribers.) 
> Do I have to code anything to tell ActiveMQ to keep messages (in the event
> a durable subscriber is established)?
> 
> What if my app is running for the first time (and not a situation where
> there was a connection, then disconnection).  In this case, is it possible
> to "catch up" on older messages when the app was launched too late to
> receive them when they were live?
> 

Never mind about the durable subscriptions.  it turns out, the older
messages *were* being delivered, but they were delivered before the GUI was
built and so the GUI couldn't reflect this like it does when messages arrive
after the GUI is created.  Thus, the older messages were being ignored.

Mark
-- 
View this message in context: http://old.nabble.com/Persistence-not-working-tp27660206p27662790.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.