Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 84833 invoked from network); 29 Feb 2008 15:34:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Feb 2008 15:34:16 -0000 Received: (qmail 65623 invoked by uid 500); 29 Feb 2008 15:34:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 65450 invoked by uid 500); 29 Feb 2008 15:34:11 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 65441 invoked by uid 99); 29 Feb 2008 15:34:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 07:34:11 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Feb 2008 15:33:45 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DC225234C050 for ; Fri, 29 Feb 2008 07:33:17 -0800 (PST) Message-ID: <2138102823.1204299197900.JavaMail.jira@brutus> Date: Fri, 29 Feb 2008 07:33:17 -0800 (PST) From: "Dan Checkoway (JIRA)" To: dev@activemq.apache.org Subject: [jira] Issue Comment Edited: (AMQ-499) Support for delayed/scheduled delivery of messages. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41477#action_41477 ] dcheckoway edited comment on AMQ-499 at 2/29/08 7:31 AM: ------------------------------------------------------------ I'd like to add my name to the list of folks who would greatly appreciate this feature. The requirement on my end is to support queueing a message that will get handled at some fixed point in time in the future. As it stands now, I have to hack around this by having multiple queues, each dedicated to delaying a certain amount of time. i.e. a 1-minute, 5-minute, 30-minute, and 60-minute queue. Separate threads periodically poll these queues, at a frequency respective with the intended delay. If a message needs to be delayed 4:23:00 in the future, first it goes into the 60-minute queue, and bounces there 4 times...then into the 5-minute queue 4x, then the 1-minute queue 3x. etc. Ugly!! Anyway, if you could implement the "TimeToDeliver" type feature in ActiveMQ it would be much appreciated! was (Author: dcheckoway): I'd like to add my name to the list of folks who would greatly appreciate this feature. The requirement on my end is to support queueing a message that will get handled at some fixed point in time in the future. As it stands now, I have to hack around this by having multiple queues, each dedicated to delaying a certain amount of time. i.e. a 1-minute, 5-minute, 30-minute, and 60-minute queue. Separate threads periodically poll these queues, at a frequency respective with the intended delay. If a message needs to be delayed 4:23 in the future, first it goes into the 60-minute queue, and bounces there 4 times...then into the 5-minute queue 4x, then the 1-minute queue 3x. etc. Ugly!! Anyway, if you could implement the "TimeToDeliver" type feature in ActiveMQ it would be much appreciated! > Support for delayed/scheduled delivery of messages. > --------------------------------------------------- > > Key: AMQ-499 > URL: https://issues.apache.org/activemq/browse/AMQ-499 > Project: ActiveMQ > Issue Type: New Feature > Components: Broker > Reporter: Hiram Chirino > Fix For: 5.2.0 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.