activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1160) provide a way of setting the timeToLive from the point in time the message is received by the broker to avoid clock sync issues
Date Mon, 30 Jul 2007 16:05:49 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Davies resolved AMQ-1160.
-----------------------------

    Fix Version/s:     (was: 5.1.0)
                   5.0.0
       Resolution: Fixed

> provide a way of setting the timeToLive from the point in time the message is received
by the broker to avoid clock sync issues
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1160
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1160
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: James Strachan
>            Assignee: Rob Davies
>             Fix For: 5.0.0
>
>
> The JMS default is to use timeToLive relative to the client send; which means things
get converted to GMT and can suffer from clock sync issues.
> A useful alternative could be to set the timeToLive on a message relative to the broker's
clock when it receives it. That way there's no need to rely on a properly sync'd clock.
> So we could either 
> * use a new header - ActiveMQBrokerTimeToLive or something.
> * use a negative time to live value to indicate, its the time to live relative to the
broker (rather than relative to the client)
> Am wondering if the negative timeToLive value would break any existing software? (Currently
we tend to ignore any TTL values less than or equal to zero)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message