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-1162) Non-persistent messages on a Queue expire prior to TimeToLive for small values
Date Mon, 30 Jul 2007 21:13:49 GMT

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

Rob Davies resolved AMQ-1162.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0

> Non-persistent messages on a Queue expire prior to TimeToLive for small values 
> -------------------------------------------------------------------------------
>
>                 Key: AMQ-1162
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1162
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: AMQ - 3.2.1; Client - Windows XP SP 2; JRE1.5.0_06 
> Broker - Windows XP SP 2 or Linux RedHat 8.0
>            Reporter: Bruce Craigie
>            Assignee: Rob Davies
>             Fix For: 5.0.0
>
>
> In ActiveMQ3.2.1 non-persistent messages on a Queue expire prior to TimeToLive for relatively
small values. 
> I assume the cause is clock discrepancies between the client and broker machines.. 
> The objective of timeToLive is to determine how long the Broker retains a message before
discarding it. 
> Since clock differences can be significant and since the original message TimeToLive
and the original message timeStamp do have a common reference(clock), it would seem to make
sense for the Broker to recalculate the timeToLive based on the difference of these two values.
> SEE ALSO: Bug AMQ-975

-- 
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