Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 26 Oct 2016 01:31:58 +0000 (UTC)
From: "John D. Ament (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.13015206.1477423671000.85082.1477445518335@Atlassian.JIRA>
In-Reply-To: <JIRA.13015206.1477423671000@Atlassian.JIRA>
References: <JIRA.13015206.1477423671000@Atlassian.JIRA> <JIRA.13015206.1477423671471@arcas>
Subject: [jira] [Commented] (ARTEMIS-821) Support scheduled messages with
 the STOMP protocol
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Oct 2016 01:32:00 -0000


    [ https://issues.apache.org/jira/browse/ARTEMIS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15607031#comment-15607031 ] 

John D. Ament commented on ARTEMIS-821:
---------------------------------------

I'm not going to be able to get to this in the next day or so.... but if someone wants to take a look, did some digging.

AMQP supports this in the {{x-opt-delivery-time}} or {{x-opt-delivery-delay}} headers, which get mapped into the JMS message (core message) as a long property, ala {{jms.setLongProperty(HDR_SCHEDULED_DELIVERY_TIME.toString(), deliveryTime);}} (take a look at {{InboundTransformer}} line 110 ish for context).

ActiveMQ 5.x supports something similar with AMQ specific headers, based on http://activemq.apache.org/nms/stomp-delayed-and-scheduled-message-feature.html , probably where the SO poster got these from.

The simplest way forward (and perhaps someone could validate) may be to update {{copyStandardHeadersFromFrameToMessage}} in {{StompUtils}} to read these headers as well.

> Support scheduled messages with the STOMP protocol
> --------------------------------------------------
>
>                 Key: ARTEMIS-821
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-821
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>    Affects Versions: 1.4.0
>            Reporter: Jiri Danek
>            Priority: Blocker
>             Fix For: 1.5.0
>
>
> Scheduled messages are already supported with Core and with AMQP. Scheduled messages are JMS 2.0 feature.
> I would like to request their support in STOMP protocol. This feature has been also requested in [a Stack Overflow question|http://stackoverflow.com/q/38996576/6081394].


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)