activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6121) Messages can continually expire from DLQ and back
Date Mon, 11 Jan 2016 15:58:39 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092181#comment-15092181
] 

ASF subversion and git services commented on AMQ-6121:
------------------------------------------------------

Commit 66cfc7bab3dfa2e079bbc5276312c97ab02cae4f in activemq's branch refs/heads/master from
[~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=66cfc7b ]

AMQ-6121
AMQ-6122

Prevent messages on DLQ for looping back onto the same DLQ.  Prevents
expired messages from bouncing back and duplicate messages from the
store from causing a deadlock.

> Messages can continually expire from DLQ and back
> -------------------------------------------------
>
>                 Key: AMQ-6121
>                 URL: https://issues.apache.org/jira/browse/AMQ-6121
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-leveldb-store, Broker, Message Store
>    Affects Versions: 5.13.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.13.1
>
>
> In some cases it is possible for a message on the DLQ to retain its expiration value
such as when LevelDB reads a duplicate from the store.  In these cases the message can end
up being expired and sent back to the DLQ over and over.  This leads to inaccurate statistics
on the DLQ among other things.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message