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] (ARTEMIS-1650) Improve paged message acknowledge
Date Fri, 09 Feb 2018 17:11:00 GMT

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

ASF subversion and git services commented on ARTEMIS-1650:
----------------------------------------------------------

Commit 63e0c0d310850fb59f800d2cc5cf9c5cfc0060ec in activemq-artemis's branch refs/heads/master
from Clebert Suconic
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=63e0c0d ]

ARTEMIS-1650 Fixing Testsuite on PageReference

Transactions may initialize a PagedReference without a valid message yet
during load of prepared transactions.

Caching has to be lazy on this case and it should load on demand.


> Improve paged message acknowledge
> ---------------------------------
>
>                 Key: ARTEMIS-1650
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1650
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: shoukun huai
>            Priority: Minor
>         Attachments: jstack.txt
>
>
> PagedMessage may be GCed before it was acknowledged. In this case, server has to reload
the page and hold the page cache lock, then block other consumers of the same queue.
> When do acknowledge, we need at least message id, transaction id, and is large message.
> We believe the three property can be added to PagedReference, so we do not rely on PagedMessage
when acknowledge except LargeMessage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message