activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik (JIRA)" <>
Subject [jira] [Reopened] (AMQ-4468) TimeStampPlugin doesn't work with Stomp
Date Tue, 14 May 2013 22:27:15 GMT


Erik reopened AMQ-4468:

Steps to reproduce the problem:

1) Enable TimeStampPlugin
2) Send a message to a topic with the timestamp header set to -1 day earlier and the expire
header set to -1 day + 10 minutes using the STOMP protocol. JMS will not work.
4) Use the http://<>:8161/admin interface to see that the message is not present, or
use active-admin browse to verify the message is not located in the topic.

Further details of how the timestampplugin should work can be found here:
. Timestampplugin does not work as expected in this article with the STOMP protocol.

> TimeStampPlugin doesn't work with Stomp
> ---------------------------------------
>                 Key: AMQ-4468
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: stomp
>    Affects Versions: 5.8.0
>         Environment: Ubuntu 12.04.1 LTS Precise, OpenJDK Runtime Environment (IcedTea7
2.3.3) (7u9-2.3.3-0ubuntu1~12.04.1)
>            Reporter: Erik
>            Assignee: Timothy Bish
>            Priority: Minor
>              Labels: JMSExpiration, JMSExpires, JMSTimestamp, TimeStampPlugin, activemq,
disableTimeStampsByDefault, expires, stomp, timestamp
>         Attachments:
> Stomp producers cannot set the JMSTimestamp or timestamp header. Activemq always adds
a timestamp header and overrides a set value. Therefore, the expires header cannot be recalculated
according to Activemq time according to the description for TimeStampPlugin. TimeStampPlugin
works for JMS producers because the JMSExpiration UTC can be adjusted up/down according to
the difference between JMSTimestamp and Activemq UTC.
> Example:
> ActiveMQ time is 2pm UTC
> Stomp producer time is 1:03pm UTC.
> Stomp expires time is 1:03pm + 15 minutes: 1:18pm UTC.
> ActiveMQ will throw this message away with TimeStampPlugin enabled.
> ActiveMQ will deliver this message for a JMSProducer.
> Recommendation:
> 1)
> ActiveMQ should allow Stomp producers to set a timestamp or JMSTimestamp header.
> if( Stomp Message Timestamp Header ) {
> use header
> }
> else {
> add timestamp header
> }
> 2)
> Add the disableTimeStampsByDefault=true feature to the stomp protocol URI.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message