Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com
 designates 64.233.184.239 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=c/zcjdiqdN52EqfnNC38nJgWS7zEVzuka4Y5ECRTtDXNsuaT8+DBe5Jmw5vz+W5/aZGJPZTnSwSACsUIchohCFiqBNY+rQHBT5QwypX7bWcmqDRwPfh2zBB0xl88JIRX9uJtIZTy1PcFbUB3davsbio0QlvEVKmrAeYS0zdMhUE=
Message-ID: <ec6e67fd0612070900y3b543350gdc71ee7fb52f764f@mail.gmail.com>
Date: Thu, 7 Dec 2006 17:00:12 +0000
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Inaccessible Messages in Queue
In-Reply-To: <ec6e67fd0612070859o7e95d907n60a689fc7cbbabfc@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: 
 <OF53C34172.FD668668-ON8525723C.006F64D8-8525723C.0071AEAA@jpmchase.com>
	 <ec6e67fd0612070859o7e95d907n60a689fc7cbbabfc@mail.gmail.com>

BTW if you bounce the broker, messages are redispatched - but the real
fix is to upgrade to 4.1.0

On 12/7/06, James Strachan <james.strachan@gmail.com> wrote:
> Yes I've seen this before - its a bug in the dispatch logic. It was
> fixed in 4.1.0.
>
> On 12/6/06, tony.x.rippy@jpmchase.com <tony.x.rippy@jpmchase.com> wrote:
> > Hello,
> >
> > I'm seeing a strange issue with ActiveMQ 4.0.2. We have a single process
> > that generates messages and sends them to a queue. There are several
> > hundred client processes that consume messages from this queue. I have set
> > the queue prefetch policy of the client connections to 1,
> > useRetroactiveConsumer = true, maxInactivityDuration = 0. I'm using a
> > non-transacted auto-acknowledge session with the MessageConsumer.
> >
> > Every now and then we get what appears to be a "lost" message. The clients
> > are unable to pull any more messages off the queue, but JConsole/JMX is
> > reporting that there is 1 message still available. Using the browseAsTable
> > operation I'm able to inspect the message, but nothing seems out of the
> > ordinary.
> >
> > Has anyone seen a situation like this before? Any suggestions of what I
> > could do to prevent this from happening?
> >
> > Thanks in advance,
> >
> > Tony
> >
> >
> > -----------------------------------------
> > This transmission may contain information that is privileged,
> > confidential, legally privileged, and/or exempt from disclosure
> > under applicable law.  If you are not the intended recipient, you
> > are hereby notified that any disclosure, copying, distribution, or
> > use of the information contained herein (including any reliance
> > thereon) is STRICTLY PROHIBITED.  Although this transmission and
> > any attachments are believed to be free of any virus or other
> > defect that might affect any computer system into which it is
> > received and opened, it is the responsibility of the recipient to
> > ensure that it is virus free and no responsibility is accepted by
> > JPMorgan Chase & Co., its subsidiaries and affiliates, as
> > applicable, for any loss or damage arising in any way from its use.
> > If you received this transmission in error, please immediately
> > contact the sender and destroy the material in its entirety,
> > whether in electronic or hard copy format. Thank you.
> >
> >
>
>
> --
>
> James
> -------
> http://radio.weblogs.com/0112098/
>


-- 

James
-------
http://radio.weblogs.com/0112098/