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 2021/09/24 20:44:00 UTC
[jira] [Work logged] (ARTEMIS-3498) Bridge will not discount
delivering counts on internal queues
[ https://issues.apache.org/jira/browse/ARTEMIS-3498?focusedWorklogId=655086&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-655086 ]
ASF GitHub Bot logged work on ARTEMIS-3498:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Sep/21 20:43
Start Date: 24/Sep/21 20:43
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #3774:
URL: https://github.com/apache/activemq-artemis/pull/3774
--
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.
To unsubscribe, e-mail: gitbox-unsubscribe@activemq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 655086)
Remaining Estimate: 0h
Time Spent: 10m
> Bridge will not discount delivering counts on internal queues
> -------------------------------------------------------------
>
> Key: ARTEMIS-3498
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3498
> Project: ActiveMQ Artemis
> Issue Type: Task
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> if the queue is internal, a Bridge (or a ClusterConnectionBridge) will keep delivering counts higher than what they are supposed to after a reconnection.
> We had tests validating this on Bridge, however I missed the internal queue scenario and I ended up missing the assertion and checks for the Clustered Bridge).
> Tests added will show the issue and prevent further issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)