Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of james.strachan@gmail.com
 designates 66.249.92.168 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=swQIKR7mrDJzpd/M1Z9MBoATSPoxqHlqrqu35RRy2yJ8E1asxk2yICaMrZO5el/EfHaseZ6W1yhNDuZ6wI6Of52UGH8PmbFaUz/epLr9vQbk1jpurZr/cto+7QEWJFAI7u//PQQfU3c7h4rW6yL9PAtka6vlwYGPxdehn97mlbA=
Message-ID: <ec6e67fd0604281015y5e24dce9s6fd86c53c0996ce6@mail.gmail.com>
Date: Fri, 28 Apr 2006 18:15:10 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: activemq-users@geronimo.apache.org
Subject: Re: Delay Message Processing
In-Reply-To: <4143283.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4143283.post@talk.nabble.com>

I'd use a scheduler (like Quartz) to send the message

http://www.opensymphony.com/quartz/

we currently don't have any efficient ways to send a message for
dispatching in the future.

It wouldn't be too hard to add a special Broker Interceptor to deal
with 'future messages' where some JMS message header could be used to
define the time at which a message should be dispatched. Then
internally the interceptor would filter out these messages and create
a new timer event in Quartz.

http://activemq.org/Interceptors

A simple implementation could just be to persist the message inside
quartz as the timer event state; a more clever and efficient
implementation would be to use ActiveMQ for the persistence and then
use the timer event to start the dispatching of the message. Though
this might involve some change to the ActiveMQ broker code to be able
to persist messages that should not be dispatched.


On 4/28/06, osian <osian@osian.me.uk> wrote:
>
> Is there any way in which to tell ActiveMQ when producing a message that =
this
> message is not to be processed until a set date/time. I have considered
> validating the message, and if it is not ready to process, produce a new
> message (and this will go on until it is ready to be processed), but this=
 is
> a large overhead for a simple problem.  Any advice would be greatfully
> appreciated,
>
> Cheers,
> Osh
> --
> View this message in context: http://www.nabble.com/Delay-Message-Process=
ing-t1525423.html#a4143283
> Sent from the ActiveMQ - User forum at Nabble.com.
>
>


--

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