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 GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/10 16:35:00 UTC

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

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

ASF GitHub Bot logged work on ARTEMIS-2650:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Mar/20 16:34
            Start Date: 10/Mar/20 16:34
    Worklog Time Spent: 10m 
      Work Description: brusdev commented on pull request #3011: ARTEMIS-2650 The delivering count is wrong after reconnecting an openwire client
URL: https://github.com/apache/activemq-artemis/pull/3011
 
 
   Fix the conversion of the message id from the CORE messages.
   Fix the credits acquired for acknowledges related to undelivered messages.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 400825)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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 Bruscino
>            Priority: Major
>          Time Spent: 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)