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

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

                Author: ASF GitHub Bot
            Created on: 30/Aug/19 06:49
            Start Date: 30/Aug/19 06:49
    Worklog Time Spent: 10m 
      Work Description: wy96f commented on issue #2703: ARTEMIS-2380 Fix 
delivering message in the case of consume close
URL: https://github.com/apache/activemq-artemis/pull/2703#issuecomment-526481239
 
 
   > You may have multiple consumers on a single ip... relying on ip doesnt 
sound safe way to link to a single consumer
   
   Once we know ip, we can let users take thread dumps of their process. Most 
likely something hangs in business logic, resulting in session not committed, 
this way they can quickly fix the issue. 
 
----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 304069)
    Time Spent: 5h 50m  (was: 5h 40m)

> Fix delivering message in the case of consume close
> ---------------------------------------------------
>
>                 Key: ARTEMIS-2380
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2380
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: yangwei
>            Priority: Major
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> When consumer is closed and transaction is not committed or rollbacked, the 
> msg acked is not showed by delivering message but counted by delivering count.
> We add closed consumer if any message is acked but not committed or 
> rollbacked, and remove closed consumer if transaction is finished. In this 
> way, delivering messages can be properly retained.
> During calling hasCosnumer and getConsumerId, there is some race condition 
> that emptyConsumerId is called causing following getConsumerId throws 
> IllegalStateException. Also optimize it without extra effort.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to