Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of tabish121@gmail.com designates
 209.85.128.171 as permitted sender)
Message-ID: <515248F5.5070104@gmail.com>
Date: Tue, 26 Mar 2013 21:18:45 -0400
From: Timothy Bish <tabish121@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Re: persistent message missing to a durable subscriber when it
 reconnects(restarts)
References: <1364279991802-4665130.post@n4.nabble.com>
 <CAKS7T5MjzaxnXQ9NHmsP4FOO4_+stscgwgiNZHO5++Ph+b+vWA@mail.gmail.com>
 <1364320951942-4665159.post@n4.nabble.com>
 <CAKS7T5O8TB3ppqPNOg1VL=3pTKNp_aX45-U+d-Wun=_sxT5jyg@mail.gmail.com>
 <1364345368497-4665166.post@n4.nabble.com>
In-Reply-To: <1364345368497-4665166.post@n4.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 03/26/2013 08:49 PM, Jaewoong Choi wrote:
> Unfortunately, I couldn't verify if the latest snapshots resolved the issue I
> questioned.  I failed to replace the activemq-core dependency from 5.7.0 to
> any upper versions as I ended up facing some runtime errors with the API
> I've used with 5.7.0.  It looks like, including "broker/client split" that
> you mentioned, from 5.8.0 the activemq is not that backward compatible with
> 5.7.0 and below versions.

You probably didn't include the activemq-kahadb-store jar there's also 
the activemq-all uber module which will bring in everything.

>
> I have a different question (but for the same purpose: to resolve this
> issue).  Is there any event handler interface the ActiveMQ provides and I
> can hook up, such that I can control store cursors (e.g. AbstractStoreCursor
> or TopicStorePrefetch instances) in its implementation?  The event of the
> interest is "on consumer closing" (or "deactivation of the durable
> subscription") in relation with this question thread, so that I can simply
> wipe out the store cursor's pending list whenever the subscriber closes it
> subscription.  To me, reclaiming all inflight messages back to the store
> cursor's pending list that the current ActiveMQ approaches seems just too
> complicated and not straight forward.  I'd rather just clean up the pending
> list (store cursor cache) whenever the subscriber closes on the client side
> (i.e. subscription becomes deactivated in broker) in order to avoid mess up
> the store cursor's internal states...
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/persistent-message-missing-to-a-durable-subscriber-when-it-reconnects-restarts-tp4665130p4665166.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>


-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/