[
https://issues.apache.org/jira/browse/ARTEMIS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615607#comment-15615607
]
Jiri Danek commented on ARTEMIS-821:
------------------------------------
I thought that specifying relative delay instead of absolute time is a way to
deal with the possibility of clock skew between clients and server. Another
illusion shattered. :I
This is yet another strange thing related to this. Section 7.9. of JMS 2.0
Spec: "Note however that the setDeliveryDelay method on Message cannot be used
to set the delivery delay of a message." What?!? Why they even put the method
there, then, if it does not do what it is supposed to do?
> 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)
