[
https://issues.apache.org/jira/browse/ARTEMIS-3557?focusedWorklogId=689914&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-689914
]
ASF GitHub Bot logged work on ARTEMIS-3557:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/21 11:09
Start Date: 03/Dec/21 11:09
Worklog Time Spent: 10m
Work Description: gtully commented on a change in pull request #3858:
URL: https://github.com/apache/activemq-artemis/pull/3858#discussion_r761845128
##########
File path:
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/cluster/distribution/ClusterTestBase.java
##########
@@ -751,6 +762,10 @@ protected void sendInRange(final int node,
message.putStringProperty(ClusterTestBase.FILTER_PROP, new
SimpleString(filterVal));
}
+ if (routingType != null) {
Review comment:
that may be some special case that requires a sent message to have a
routing semantic, it is not normal. Typically a message goes to an address, and
the address has a routing type configured across bindings. Ie: it is the broker
that determines how a message is routed.
It is non typical to call setRoutingType - it should not be necessary. From
a quick peek at git - ARTEMIS-1068 introduced that setter for AMQP, probably
for some amqp to jms mapping scenario. But it should not be used or required in
this scenario.
I think, have another look.
--
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: 689914)
Time Spent: 3h 50m (was: 3h 40m)
> ARTEMIS-1925 fix does not handle redistribution to "old" consumers
> ------------------------------------------------------------------
>
> Key: ARTEMIS-3557
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3557
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> OFF_WITH_REDISTRIBUTION does not handle this scenario:
> If a destination and consumer exist on one node in a cluster and a producer
> shows up on another node messages will not get redistributed until the old
> consumer disconnects and reconnects.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
