[
https://issues.apache.org/activemq/browse/AMQ-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-2646.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.4.0
Fixed by SVN revision 924661
> Support Schedule and Delay properties in Stomp headers
> ------------------------------------------------------
>
> Key: AMQ-2646
> URL: https://issues.apache.org/activemq/browse/AMQ-2646
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.4.0
> Reporter: Michael Justin
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.4.0
>
>
> following http://activemq.apache.org/delay-and-schedule-message-delivery.html
> I tried to delay a message using a AMQ_SCHEDULED_DELAY header property.
> The Stomp frames look like this:
> send:
> CONNECT
> received:
> CONNECTED
> session:ID:mj-PC-49610-1268150511998-3:10
> send:
> SUBSCRIBE
> destination:/queue/Habari
> ack:auto
> id:{AD4DFED5-B508-41B6-9AE2-F43E890A2522}
> send:
> SEND
> destination:/queue/Habari
> AMQ_SCHEDULED_DELAY:2000
> test msg
> --
> After the SEND message, the broker interrupts the connection. If I remove the
> header property, the broker sends the message immediately as usual. So I
> guess that the Stomp code handles the new header property in an unexpected
> way. If I find the time I'll have a look at the source code.
> See also: "Delay messages with Stomp: broker resets connection when
> AMQ_SCHEDULED_DELAY header is specified "
> http://old.nabble.com/Delay-messages-with-Stomp%3A-broker-resets-connection-when-AMQ_SCHEDULED_DELAY-header-is-specified-td27837862.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
