You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Craigie (JIRA)" <ji...@apache.org> on 2007/02/14 03:02:02 UTC
[jira] Created: (AMQ-1162) Non-persistent messages on a Queue
expire prior to TimeToLive for small values
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
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
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.
[jira] Assigned: (AMQ-1162) Non-persistent messages on a Queue
expire prior to TimeToLive for small values
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1162:
-------------------------------
Assignee: Rob Davies
> 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
>
> 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.
[jira] Resolved: (AMQ-1162) Non-persistent messages on a Queue
expire prior to TimeToLive for small values
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ 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.