[
https://issues.apache.org/jira/browse/ARTEMIS-3502?focusedWorklogId=659532&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-659532
]
ASF GitHub Bot logged work on ARTEMIS-3502:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Oct/21 12:41
Start Date: 04/Oct/21 12:41
Worklog Time Spent: 10m
Work Description: gemmellr commented on a change in pull request #3777:
URL: https://github.com/apache/activemq-artemis/pull/3777#discussion_r721324935
##########
File path:
artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/SingleServerTestBase.java
##########
@@ -42,6 +42,7 @@ public void setUp() throws Exception {
super.setUp();
server = createServer();
+ server.getConfiguration().setAddressQueueScanPeriod(100);
Review comment:
Its not all about the time, but rather more that essentially _every_
test [not testing this] is now running with a non-represeatative broker config,
which is something I think should generally be avoided - and is particularly
shown up by the other tests that then had to artificially increase it again
because it was set unexpectedly low everywhere by changes like this.
If the default is 30sec then only tests verifying this stuff should need to
be setting the config (and then, typically lower than this 100ms).
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 659532)
Time Spent: 2h 40m (was: 2.5h)
> Auto delete of a queue could lead to inconsistencies
> ----------------------------------------------------
>
> Key: ARTEMIS-3502
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3502
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Major
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Auto delete might happen after a disconnect of consumers.
> on a situation where the consumer was up to date the queue could be removed,
> leading to a few issues.
> we should improve how we handle with auto-delete and avoid these
> inconsistencies.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
