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 gary.tully@gmail.com designates
 209.85.218.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=lGgIB314SDszhqthBt85+9+/MJL1w+aTNBlHnRz++sxkW+E+eegowoc+8Qj8yZZ8uW
         UiKh6FIY3oczerPA5vzj9DiD6VCU89flit/jFQr5IYz+m7Zxz9BFPtFLwDFsZT5Q0T1s
         yXg8s2BBznQESQJPdPXyt5dqPFwAT0e14gyXU=
MIME-Version: 1.0
In-Reply-To: <4BC4BB59.90303@e-dialog.com>
References: <4BC4BB59.90303@e-dialog.com>
Date: Wed, 14 Apr 2010 10:15:42 +0100
Message-ID: <n2o3a73c17c1004140215za2ba990fkdd9794d68d54cdf6@mail.gmail.com>
Subject: Re: Messages stuck after Client host reboot
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org, jcarlson@e-dialog.com
Content-Type: multipart/alternative; boundary=0016e6db7ba28ae81704842ed267

--0016e6db7ba28ae81704842ed267
Content-Type: text/plain; charset=ISO-8859-1

The re-dispatch is triggered by the tcp connection dying, netstat can help
with the diagnosis here. Check the connection state of the broker port after
the client host is rebooted, if the connection is still active, possibly in
a timed_wait state, you may need to configure some additional timeout
options on the broker side.

On 13 April 2010 19:43, Josh Carlson <jcarlson@e-dialog.com> wrote:

> I am using client acknowledgements with a prefetch size of 1 with no
> message expiration policy. When a consumer subscribes to a queue I can see
> that the message gets dispatched correctly. If the process gets killed
> before retrieving and acknowledging the message I see the message getting
> re-dispatched (correctly). I expected this same behaviour if the host
> running the process gets rebooted or crashes. However, after reboot I can
> see that the message is stuck in the dispatched state to the consumer that
> is long gone. Is there a way that I can get messages re-dispatched when a
> host hosting consumer processes gets re-booted? How does it detect the case
> when a process dies (even with SIGKILL)?
>
> I did notice that if I increase my prefetch size and enqueue another
> message after the reboot, that activemq will re-dispatch the original
> message. However with prefetch size equal to one the message never seems to
> get re-dispatched.
>


-- 
http://blog.garytully.com

Open Source Integration
http://fusesource.com

--0016e6db7ba28ae81704842ed267--