You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/06/02 15:24:00 UTC

[jira] [Commented] (ARTEMIS-2650) The delivering count is wrong after reconnecting an openwire client

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

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

Commit 815f383f9c19abacd0c56543ebc0e93e06dffbf9 in activemq-artemis's branch refs/heads/main from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=815f383 ]

ARTEMIS-3234 - revisit fix to deal with credit on unmatched acks, thanks to brusdev for the interceptor feature and test from ARTEMIS-2650


> The delivering count is wrong after reconnecting an openwire client
> -------------------------------------------------------------------
>
>                 Key: ARTEMIS-2650
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2650
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Domenico Francesco Bruscino
>            Priority: Major
>             Fix For: 2.12.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> In an environment using OpenWire clients and messages sent by a CORE producer, we see that messages get prefetched out to the consumer up to its prefetch limit. However, after the client reconnects the delivering count is displayed as prefetch+1.
> After the consumer reconnection, the broker receives a message ack for a message dispatched before the disconnection. This ack causes an invalid acquiring of credits and a wrong message dispatching.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)