[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[ https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858816=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858816 ] ASF GitHub Bot logged work on ARTEMIS-4247: --- Author: ASF GitHub Bot Created on: 25/Apr/23 01:14 Start Date: 25/Apr/23 01:14 Worklog Time Spent: 10m Work Description: clebertsuconic commented on PR #4443: URL: https://github.com/apache/activemq-artemis/pull/4443#issuecomment-1521024403 addressing comments at https://github.com/apache/activemq-artemis/pull/4445 Issue Time Tracking --- Worklog Id: (was: 858816) Time Spent: 4h 10m (was: 4h) > Inconsistencies between AMQP Mirror and Artemis Clustering > -- > > Key: ARTEMIS-4247 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4247 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Clebert Suconic >Priority: Major > Time Spent: 4h 10m > Remaining Estimate: 0h > > - activemq.notifications are being transferred to the target node, unless an > ignore is setup > - topics are being duplicated after redistribution > - topics sends are being duplicated when a 2 node cluster mirrors to another > 2 node cluster, and both nodes are mirrored. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9249) Remove joram-jms-tests
Matt Pavlovich created AMQ-9249: --- Summary: Remove joram-jms-tests Key: AMQ-9249 URL: https://issues.apache.org/jira/browse/AMQ-9249 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich 1. The joram-jms-tests are redundant in the activemq-unit-tests 2. activemq-amqp will need to be updated/refactored to handle not using joram as much of a baseline -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9239) Jakarta JMS package namespace for broker
[ https://issues.apache.org/jira/browse/AMQ-9239?focusedWorklogId=858806=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858806 ] ASF GitHub Bot logged work on AMQ-9239: --- Author: ASF GitHub Bot Created on: 25/Apr/23 00:04 Start Date: 25/Apr/23 00:04 Worklog Time Spent: 10m Work Description: mattrpav commented on PR #1002: URL: https://github.com/apache/activemq/pull/1002#issuecomment-1520973242 @gemmellr I think removing it would be a good end goal. However, right now its deeply integrated into amqp tests. I'll make a JIRA for removing joram and refactoring the amqp tests post-jakarta work. Issue Time Tracking --- Worklog Id: (was: 858806) Time Spent: 1h (was: 50m) > Jakarta JMS package namespace for broker > > > Key: AMQ-9239 > URL: https://issues.apache.org/jira/browse/AMQ-9239 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[
https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858802=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858802
]
ASF GitHub Bot logged work on ARTEMIS-4247:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 22:23
Start Date: 24/Apr/23 22:23
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on code in PR #4443:
URL: https://github.com/apache/activemq-artemis/pull/4443#discussion_r1175831966
##
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/connect/mirror/AMQPMirrorControllerSource.java:
##
@@ -76,14 +77,20 @@ public class AMQPMirrorControllerSource extends
BasicMirrorController im
public static final Symbol INTERNAL_ID =
Symbol.getSymbol("x-opt-amq-mr-id");
public static final Symbol INTERNAL_DESTINATION =
Symbol.getSymbol("x-opt-amq-mr-dst");
+ /** When a clustered node (from regular cluster connections) receives a
message
+ it will have target queues associated with it
+ this could be from message redistribution or simply load balancing.
+ an that case this will have the queue associated with it */
+ public static final Symbol TARGET_QUEUES =
Symbol.getSymbol("x-opt-amq-trg-q");
Review Comment:
the PR I sent is addressing this.
Issue Time Tracking
---
Worklog Id: (was: 858802)
Time Spent: 4h (was: 3h 50m)
> Inconsistencies between AMQP Mirror and Artemis Clustering
> --
>
> Key: ARTEMIS-4247
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4247
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 4h
> Remaining Estimate: 0h
>
> - activemq.notifications are being transferred to the target node, unless an
> ignore is setup
> - topics are being duplicated after redistribution
> - topics sends are being duplicated when a 2 node cluster mirrors to another
> 2 node cluster, and both nodes are mirrored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4254) Transactional / Replication Soak Test
Clebert Suconic created ARTEMIS-4254: Summary: Transactional / Replication Soak Test Key: ARTEMIS-4254 URL: https://issues.apache.org/jira/browse/ARTEMIS-4254 Project: ActiveMQ Artemis Issue Type: Test Reporter: Clebert Suconic I recently developed a replication test under soak-test to validate producing into a topic a failing over during the producers. Even though I did not find anything wrong with the test, I am still committing the test. (There is not enough testing, so... just one more to ensure transaction and replication). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4253) disabling a few ActiveMQServerControlUsingCoreTest tests
Clebert Suconic created ARTEMIS-4253: Summary: disabling a few ActiveMQServerControlUsingCoreTest tests Key: ARTEMIS-4253 URL: https://issues.apache.org/jira/browse/ARTEMIS-4253 Project: ActiveMQ Artemis Issue Type: Test Reporter: Clebert Suconic some of these tests are adding noise to the test. For example you count how many sessions you have, however the framework to send and receive notifications itself is creating a sessions. Some times (intermittently) these sessions are affecting the counts, what makes these tests invalid and they should be ignored on the UsingCoreTests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4212) Unexpected Behavior when Routing Type of Destinations Doesn't Match Clients
[
https://issues.apache.org/jira/browse/ARTEMIS-4212?focusedWorklogId=858753=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858753
]
ASF GitHub Bot logged work on ARTEMIS-4212:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 17:51
Start Date: 24/Apr/23 17:51
Worklog Time Spent: 10m
Work Description: jbertram commented on code in PR #4421:
URL: https://github.com/apache/activemq-artemis/pull/4421#discussion_r1175612740
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/amqp/QueueAutoCreationTest.java:
##
@@ -124,7 +124,7 @@ public void testAutoCreateOnTopic() throws Exception {
Connection connection = factory.createConnection();
SimpleString addressName =
UUIDGenerator.getInstance().generateSimpleStringUUID();
logger.debug("Address is {}", addressName);
- clientSession.createAddress(addressName, RoutingType.ANYCAST, false);
+ clientSession.createAddress(addressName, RoutingType.MULTICAST, false);
Review Comment:
You're right that is strange. Both tests succeed because the address with
the wrong routing-type is automatically updated. I updated it so both tests use
the correct routing-type to being with.
Issue Time Tracking
---
Worklog Id: (was: 858753)
Time Spent: 5h 20m (was: 5h 10m)
> Unexpected Behavior when Routing Type of Destinations Doesn't Match Clients
> ---
>
> Key: ARTEMIS-4212
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4212
> Project: ActiveMQ Artemis
> Issue Type: Improvement
>Reporter: Justin Bertram
>Assignee: Justin Bertram
>Priority: Major
> Time Spent: 5h 20m
> Remaining Estimate: 0h
>
> When the routing type of an address (and associated queue) does not match the
> routing type of a client producer, the resultant behavior is a bit unexpected.
> Expected Behavior:
> If a client sends a message to an address / queue with the same name, but a
> different routing type, the expected behavior would be to throw some sort of
> InvalidDestinationException (if auto-create is not enabled), or to create the
> matching address and queue with the appropriate routing type. The routing
> count on the existing address (with non-matching routing type) should remain
> unchanged.
> Actual Behavior:
> When sending, for example, to a predefined anycast address and queue from a
> multiccast (Topic) producer, the routed count on the address is incremented,
> but the message count on the matching queue is not. No indication is given at
> the client end that the messages failed to get routed - they are silently
> dropped.
> This is reproducible using a qpid / proton queue producer to send to a
> multicast address or using a topic producer to send to an anycast address,
> e.g.:
> 1. Create a a broker, setting auto-create-queues and auto-create addresses to
> "false" for the catch-all address-setting
> 2. Start the broker and create a an address and matching queue with a ANYCAST
> routing type
> 3. Send 1000 messages to the broker using the same queue name but mismatched
> routing type:
> {code}
> ./artemis producer --url amqp://localhost:61616 --user admin --password admin
> --destination topic://{QUEUE NAME} --protocol amqp
> {code}
> No error is emitted and the routing count is incremented by 1000 at the
> address level, but remains unchanged at the destination level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (AMQ-9239) Jakarta JMS package namespace for broker
[ https://issues.apache.org/jira/browse/AMQ-9239?focusedWorklogId=858737=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858737 ] ASF GitHub Bot logged work on AMQ-9239: --- Author: ASF GitHub Bot Created on: 24/Apr/23 15:55 Start Date: 24/Apr/23 15:55 Worklog Time Spent: 10m Work Description: gemmellr commented on PR #1002: URL: https://github.com/apache/activemq/pull/1002#issuecomment-1520433766 Personally I dont see enough value in these tests to copy+convert them, a lot of it is just testing basic stuff the rest of the tests should be covering themselves. I would simply drop their usage (and did exactly that elsewhere). They dont cover any of the newer stuff, not having been updated in over a decade. I cant remember a single time theyve actually shown a failure. The actual official spec tests are easily available now unlike back then if needed. Issue Time Tracking --- Worklog Id: (was: 858737) Time Spent: 50m (was: 40m) > Jakarta JMS package namespace for broker > > > Key: AMQ-9239 > URL: https://issues.apache.org/jira/browse/AMQ-9239 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4250) ShutdownOnCriticalIOErrorMoveNextTest failing
[ https://issues.apache.org/jira/browse/ARTEMIS-4250?focusedWorklogId=858733=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858733 ] ASF GitHub Bot logged work on ARTEMIS-4250: --- Author: ASF GitHub Bot Created on: 24/Apr/23 15:06 Start Date: 24/Apr/23 15:06 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4446: URL: https://github.com/apache/activemq-artemis/pull/4446 Issue Time Tracking --- Worklog Id: (was: 858733) Time Spent: 20m (was: 10m) > ShutdownOnCriticalIOErrorMoveNextTest failing > - > > Key: ARTEMIS-4250 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4250 > Project: ActiveMQ Artemis > Issue Type: Test >Affects Versions: 2.28.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.29.0 > > Time Spent: 20m > Remaining Estimate: 0h > > ShutdownOnCriticalIOErrorMoveNextTest will simulate an IO failure, and some > of the Executors are not being cleaned. > This is an odd situation that would happen when the VM was coming down > anyway. So the test should really use a spawned VM. > The test is leaking threads, and spawning a VM would avoid these issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4250) ShutdownOnCriticalIOErrorMoveNextTest failing
[ https://issues.apache.org/jira/browse/ARTEMIS-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715868#comment-17715868 ] ASF subversion and git services commented on ARTEMIS-4250: -- Commit 0eefc38d9355e407be51cb397fef7c2f704ae330 in activemq-artemis's branch refs/heads/main from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=0eefc38d93 ] ARTEMIS-4250 Spawning VM to avoid thread leaking on ShutdownOnCriticalIOErrorMoveNextTest > ShutdownOnCriticalIOErrorMoveNextTest failing > - > > Key: ARTEMIS-4250 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4250 > Project: ActiveMQ Artemis > Issue Type: Test >Affects Versions: 2.28.0 >Reporter: Clebert Suconic >Priority: Major > Fix For: 2.29.0 > > Time Spent: 20m > Remaining Estimate: 0h > > ShutdownOnCriticalIOErrorMoveNextTest will simulate an IO failure, and some > of the Executors are not being cleaned. > This is an odd situation that would happen when the VM was coming down > anyway. So the test should really use a spawned VM. > The test is leaking threads, and spawning a VM would avoid these issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (AMQ-9239) Jakarta JMS package namespace for broker
[ https://issues.apache.org/jira/browse/AMQ-9239?focusedWorklogId=858725=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858725 ] ASF GitHub Bot logged work on AMQ-9239: --- Author: ASF GitHub Bot Created on: 24/Apr/23 14:43 Start Date: 24/Apr/23 14:43 Worklog Time Spent: 10m Work Description: mattrpav opened a new pull request, #1002: URL: https://github.com/apache/activemq/pull/1002 Currently this module is unmaintained and we need to convert it for jakarta broker support. Modules that use this module: activemq-amqp activemq-unit-tests Issue Time Tracking --- Worklog Id: (was: 858725) Time Spent: 40m (was: 0.5h) > Jakarta JMS package namespace for broker > > > Key: AMQ-9239 > URL: https://issues.apache.org/jira/browse/AMQ-9239 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9248) Host joram-jms-tests
[ https://issues.apache.org/jira/browse/AMQ-9248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9248: --- Assignee: Matt Pavlovich > Host joram-jms-tests > > > Key: AMQ-9248 > URL: https://issues.apache.org/jira/browse/AMQ-9248 > Project: ActiveMQ > Issue Type: Task >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > > Hosting the joram-jms-tests will allow us to convert these to jakarta for > 5.19.0 and maintain JDK migration easier. > Formerly hosted as part of github.com/fusesource -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (AMQ-9239) Jakarta JMS package namespace for broker
[ https://issues.apache.org/jira/browse/AMQ-9239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Pavlovich reassigned AMQ-9239: --- Assignee: Matt Pavlovich > Jakarta JMS package namespace for broker > > > Key: AMQ-9239 > URL: https://issues.apache.org/jira/browse/AMQ-9239 > Project: ActiveMQ > Issue Type: New Feature >Reporter: Matt Pavlovich >Assignee: Matt Pavlovich >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (AMQ-9248) Host joram-jms-tests
Matt Pavlovich created AMQ-9248: --- Summary: Host joram-jms-tests Key: AMQ-9248 URL: https://issues.apache.org/jira/browse/AMQ-9248 Project: ActiveMQ Issue Type: Task Reporter: Matt Pavlovich Hosting the joram-jms-tests will allow us to convert these to jakarta for 5.19.0 and maintain JDK migration easier. Formerly hosted as part of github.com/fusesource -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4252) Fix flaky QuorumFailOverTest tests
[
https://issues.apache.org/jira/browse/ARTEMIS-4252?focusedWorklogId=858717=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858717
]
ASF GitHub Bot logged work on ARTEMIS-4252:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 13:43
Start Date: 24/Apr/23 13:43
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4448:
URL: https://github.com/apache/activemq-artemis/pull/4448#discussion_r1175301832
##
artemis-server/src/test/java/org/apache/activemq/artemis/tests/util/ActiveMQTestBase.java:
##
@@ -1328,6 +1330,17 @@ protected static final void waitForComponent(final
ActiveMQComponent component,
}
}
+ protected static final void waitForBridges(final ActiveMQServer server, int
connectedBridges) throws Exception {
+ waitForBridges(server.getClusterManager().getDefaultConnection(null),
connectedBridges);
+ }
+
+ protected static final void waitForBridges(ClusterConnection
clusterConnection, int connectedBridges) throws Exception {
+ Bridge[] bridges = clusterConnection.getBridges();
Review Comment:
This doesnt look used. Is it needed? Was a quick-exit check intended but
missed?
##
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/impl/ClusterConnectionImpl.java:
##
@@ -630,6 +630,11 @@ public long getCallTimeout() {
return callTimeout;
}
+ @Override
+ public Bridge[] getBridges() {
+ return
records.values().stream().map(MessageFlowRecord::getBridge).toArray(Bridge[]::new);
Review Comment:
The 'records' field has 'recordsGuard' to protect its use in other cases. Is
that needed here?
Issue Time Tracking
---
Worklog Id: (was: 858717)
Time Spent: 20m (was: 10m)
> Fix flaky QuorumFailOverTest tests
> --
>
> Key: ARTEMIS-4252
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4252
> Project: ActiveMQ Artemis
> Issue Type: Test
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> QuorumFailOverTest tests are intermittently failing. To fix
> QuorumFailOverTest tests, we should wait for cluster bridge connections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?focusedWorklogId=858714=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858714 ] ASF GitHub Bot logged work on ARTEMIS-4251: --- Author: ASF GitHub Bot Created on: 24/Apr/23 13:18 Start Date: 24/Apr/23 13:18 Worklog Time Spent: 10m Work Description: AntonRoskvist commented on PR #4447: URL: https://github.com/apache/activemq-artemis/pull/4447#issuecomment-1520145971 Really nice addition. Haven't really looked into how it can be implemented, but there is a feature in "ActiveMQ Classic" that I think would be a great addition on top of this change. It's called "priorityBackup" ( https://activemq.apache.org/failover-transport-reference.html#priority-backup ) It has the client perform this type of failover to carry on its work, but then afterwards tries to continuously connect back to the original broker, releasing the new connection if/when it succeeds. This is good for handling client distribution across a broker cluster that sort of "persists" through maintenance, crashes, network outages etc on the broker side. Either way, this is a really nice addition as is! Issue Time Tracking --- Worklog Id: (was: 858714) Time Spent: 20m (was: 10m) > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers when all reconnect attempts fails, i.e. in a cluster composed of 2 > live servers, when the server to which the CORE client is connected goes down > the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4252) Fix flaky QuorumFailOverTest tests
[ https://issues.apache.org/jira/browse/ARTEMIS-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17715795#comment-17715795 ] ASF subversion and git services commented on ARTEMIS-4252: -- Commit ef4501292e69b782dd5eafc28e68ed24aaf463fc in activemq-artemis's branch refs/heads/main from Domenico Francesco Bruscino [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ef4501292e ] ARTEMIS-4252 Fix flaky QuorumFailOverTest tests > Fix flaky QuorumFailOverTest tests > -- > > Key: ARTEMIS-4252 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4252 > Project: ActiveMQ Artemis > Issue Type: Test >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > QuorumFailOverTest tests are intermittently failing. To fix > QuorumFailOverTest tests, we should wait for cluster bridge connections. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4252) Fix flaky QuorumFailOverTest tests
[ https://issues.apache.org/jira/browse/ARTEMIS-4252?focusedWorklogId=858712=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858712 ] ASF GitHub Bot logged work on ARTEMIS-4252: --- Author: ASF GitHub Bot Created on: 24/Apr/23 13:11 Start Date: 24/Apr/23 13:11 Worklog Time Spent: 10m Work Description: clebertsuconic merged PR #4448: URL: https://github.com/apache/activemq-artemis/pull/4448 Issue Time Tracking --- Worklog Id: (was: 858712) Remaining Estimate: 0h Time Spent: 10m > Fix flaky QuorumFailOverTest tests > -- > > Key: ARTEMIS-4252 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4252 > Project: ActiveMQ Artemis > Issue Type: Test >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > QuorumFailOverTest tests are intermittently failing. To fix > QuorumFailOverTest tests, we should wait for cluster bridge connections. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4244) Set web config using system properties
[ https://issues.apache.org/jira/browse/ARTEMIS-4244?focusedWorklogId=858696=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858696 ] ASF GitHub Bot logged work on ARTEMIS-4244: --- Author: ASF GitHub Bot Created on: 24/Apr/23 10:09 Start Date: 24/Apr/23 10:09 Worklog Time Spent: 10m Work Description: brusdev commented on PR #4440: URL: https://github.com/apache/activemq-artemis/pull/4440#issuecomment-1519837665 I added the support for binding and apps without names and a section in the `Embedded Web Server` doc. Issue Time Tracking --- Worklog Id: (was: 858696) Time Spent: 1h 10m (was: 1h) > Set web config using system properties > -- > > Key: ARTEMIS-4244 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4244 > Project: ActiveMQ Artemis > Issue Type: New Feature >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Set web config using system properties as users can set broker config, i.e. > starting the broker JVM with the option `-Dwebconfig.webContentEnabled=true` > enables the web content. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4244) Set web config using system properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4244?focusedWorklogId=858695=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858695
]
ASF GitHub Bot logged work on ARTEMIS-4244:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 10:06
Start Date: 24/Apr/23 10:06
Worklog Time Spent: 10m
Work Description: brusdev commented on code in PR #4440:
URL: https://github.com/apache/activemq-artemis/pull/4440#discussion_r1175068377
##
tests/integration-tests/src/test/java/org/apache/activemq/artemis/tests/integration/web/WebServerDTOConfigTest.java:
##
@@ -0,0 +1,93 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.activemq.artemis.tests.integration.web;
+
+import java.util.Properties;
+
+import org.apache.activemq.artemis.api.config.ActiveMQDefaultConfiguration;
+import org.apache.activemq.artemis.core.config.Configuration;
+import org.apache.activemq.artemis.core.config.impl.ConfigurationImpl;
+import org.apache.activemq.artemis.dto.AppDTO;
+import org.apache.activemq.artemis.dto.BindingDTO;
+import org.apache.activemq.artemis.dto.WebServerDTO;
+import org.junit.Assert;
+import org.junit.Test;
+
+public class WebServerDTOConfigTest {
+
+ @Test
+ public void testSetWebProperties() throws Throwable {
+ WebServerDTO webServer = new WebServerDTO();
+ Properties properties = new Properties();
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"customizer", "customizerTest");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"rootRedirectLocation", "locationTest");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"webContentEnabled", "true");
+ Configuration configuration = new ConfigurationImpl();
+ configuration.parsePrefixedProperties(webServer, "web", properties,
ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix());
+
+ Assert.assertEquals("customizerTest", webServer.getCustomizer());
+ Assert.assertEquals("locationTest", webServer.getRootRedirectLocation());
+ Assert.assertEquals(true, webServer.getWebContentEnabled());
+ }
+
+ @Test
+ public void testSetWebBindingProperties() throws Throwable {
+ WebServerDTO webServer = new WebServerDTO();
+ Properties properties = new Properties();
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.uri", "test-uri");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.clientAuth", "true");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.passwordCodec", "test-passwordCodec");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.keyStorePath", "test-keyStorePath");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.trustStorePath", "test-trustStorePath");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.includedTLSProtocols", "test-includedTLSProtocols,0");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.excludedTLSProtocols", "test-excludedTLSProtocols,1");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.includedCipherSuites", "test-includedCipherSuites,2");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.excludedCipherSuites", "test-excludedCipherSuites,3");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.keyStorePassword", "test-keyStorePassword");
+
properties.put(ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix() +
"bindings.test-binding.trustStorePassword", "test-trustStorePassword");
+ Configuration configuration = new ConfigurationImpl();
+ configuration.parsePrefixedProperties(webServer, "web",
[jira] [Work logged] (ARTEMIS-4244) Set web config using system properties
[
https://issues.apache.org/jira/browse/ARTEMIS-4244?focusedWorklogId=858694=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858694
]
ASF GitHub Bot logged work on ARTEMIS-4244:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 10:06
Start Date: 24/Apr/23 10:06
Worklog Time Spent: 10m
Work Description: brusdev commented on code in PR #4440:
URL: https://github.com/apache/activemq-artemis/pull/4440#discussion_r1175067712
##
artemis-cli/src/main/java/org/apache/activemq/artemis/cli/commands/Run.java:
##
@@ -133,6 +133,8 @@ public void deActivate() {
broker.components.add(broker.web);
}
+
server.getServer().getConfiguration().parsePrefixedProperties(broker.web,
"web", System.getProperties(),
ActiveMQDefaultConfiguration.getDefaultWebPropertyPrefix());
Review Comment:
@gtully thanks for your suggestion, I applied it.
Issue Time Tracking
---
Worklog Id: (was: 858694)
Time Spent: 50m (was: 40m)
> Set web config using system properties
> --
>
> Key: ARTEMIS-4244
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4244
> Project: ActiveMQ Artemis
> Issue Type: New Feature
>Reporter: Domenico Francesco Bruscino
>Assignee: Domenico Francesco Bruscino
>Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Set web config using system properties as users can set broker config, i.e.
> starting the broker JVM with the option `-Dwebconfig.webContentEnabled=true`
> enables the web content.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[
https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858684=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858684
]
ASF GitHub Bot logged work on ARTEMIS-4247:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 09:14
Start Date: 24/Apr/23 09:14
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4443:
URL: https://github.com/apache/activemq-artemis/pull/4443#discussion_r1175004814
##
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/MirrorOption.java:
##
@@ -0,0 +1,25 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.activemq.artemis.core.server;
+
+/** This is to be used in conjunction with RoutingContext, where we control
certain semantics during routing.
+ * */
+public enum MirrorOption {
Review Comment:
Having it occupy the 'prime real estate' of the name MirrorOption at the
very root of the code namepsace seems wrong given what its used for. Its not
for holding general options for the mirror, its a fairly niche almost-internal
routing control setting for use with RoutingContext.
Even if were left it named MirrorOption, it still seems like it would be far
nicer as a nested enum within RoutingContext, the only place it is used and
seems likely to be used. None of the impl-only code using it would change
really beyond just updating their import (probably even removing one for
RoutingContextImpl actually)
Issue Time Tracking
---
Worklog Id: (was: 858684)
Time Spent: 3h 50m (was: 3h 40m)
> Inconsistencies between AMQP Mirror and Artemis Clustering
> --
>
> Key: ARTEMIS-4247
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4247
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> - activemq.notifications are being transferred to the target node, unless an
> ignore is setup
> - topics are being duplicated after redistribution
> - topics sends are being duplicated when a 2 node cluster mirrors to another
> 2 node cluster, and both nodes are mirrored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[
https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858678=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858678
]
ASF GitHub Bot logged work on ARTEMIS-4247:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 08:43
Start Date: 24/Apr/23 08:43
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4443:
URL: https://github.com/apache/activemq-artemis/pull/4443#discussion_r1174968350
##
artemis-server/src/main/java/org/apache/activemq/artemis/core/postoffice/impl/BindingsImpl.java:
##
@@ -577,6 +599,9 @@ private String debugBindings() {
private void routeFromCluster(final Message message,
final RoutingContext context,
final byte[] ids) throws Exception {
+ if (!context.isMirrorDisabled()) {
+ context.setMirrorOption(MirrorOption.individualRoute);
+ }
Review Comment:
The use of clear looks to be semi-optional in places, e.g. this method and
ServerSessionImpl.send() only does it when the context 'isnt reusable'. Should
setting this explicitly mark it 'not reusable' ?
Issue Time Tracking
---
Worklog Id: (was: 858678)
Time Spent: 3h 40m (was: 3.5h)
> Inconsistencies between AMQP Mirror and Artemis Clustering
> --
>
> Key: ARTEMIS-4247
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4247
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> - activemq.notifications are being transferred to the target node, unless an
> ignore is setup
> - topics are being duplicated after redistribution
> - topics sends are being duplicated when a 2 node cluster mirrors to another
> 2 node cluster, and both nodes are mirrored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[
https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858677=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858677
]
ASF GitHub Bot logged work on ARTEMIS-4247:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 08:39
Start Date: 24/Apr/23 08:39
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4443:
URL: https://github.com/apache/activemq-artemis/pull/4443#discussion_r1174964467
##
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/connect/mirror/AMQPMirrorControllerSource.java:
##
@@ -76,14 +77,20 @@ public class AMQPMirrorControllerSource extends
BasicMirrorController im
public static final Symbol INTERNAL_ID =
Symbol.getSymbol("x-opt-amq-mr-id");
public static final Symbol INTERNAL_DESTINATION =
Symbol.getSymbol("x-opt-amq-mr-dst");
+ /** When a clustered node (from regular cluster connections) receives a
message
+ it will have target queues associated with it
+ this could be from message redistribution or simply load balancing.
+ an that case this will have the queue associated with it */
+ public static final Symbol TARGET_QUEUES =
Symbol.getSymbol("x-opt-amq-trg-q");
Review Comment:
Unresolving as both comments still seem applicable.
Issue Time Tracking
---
Worklog Id: (was: 858677)
Time Spent: 3.5h (was: 3h 20m)
> Inconsistencies between AMQP Mirror and Artemis Clustering
> --
>
> Key: ARTEMIS-4247
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4247
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> - activemq.notifications are being transferred to the target node, unless an
> ignore is setup
> - topics are being duplicated after redistribution
> - topics sends are being duplicated when a 2 node cluster mirrors to another
> 2 node cluster, and both nodes are mirrored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4247) Inconsistencies between AMQP Mirror and Artemis Clustering
[
https://issues.apache.org/jira/browse/ARTEMIS-4247?focusedWorklogId=858672=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858672
]
ASF GitHub Bot logged work on ARTEMIS-4247:
---
Author: ASF GitHub Bot
Created on: 24/Apr/23 08:21
Start Date: 24/Apr/23 08:21
Worklog Time Spent: 10m
Work Description: gemmellr commented on code in PR #4443:
URL: https://github.com/apache/activemq-artemis/pull/4443#discussion_r1174943429
##
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/connect/mirror/AMQPMirrorControllerSource.java:
##
@@ -357,6 +364,13 @@ private static void setProtocolData(MessageReference ref,
String brokerID, long
daMap.put(INTERNAL_DESTINATION, ref.getMessage().getAddress());
}
}
+
+ if (routingContext != null && routingContext.isMirrorIndividualRoute()) {
+ ArrayList queues = new ArrayList<>();
+ routingContext.forEachDurable(q ->
queues.add(String.valueOf(q.getName(;
+ daMap.put(TARGET_QUEUES, queues);
+ }
Review Comment:
Ok, sounds like its fine then, just wanted to check, as its not
obvious...very hard to tell stuff like that from the context if you dont
already know it.
Issue Time Tracking
---
Worklog Id: (was: 858672)
Time Spent: 3h 20m (was: 3h 10m)
> Inconsistencies between AMQP Mirror and Artemis Clustering
> --
>
> Key: ARTEMIS-4247
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4247
> Project: ActiveMQ Artemis
> Issue Type: Bug
>Reporter: Clebert Suconic
>Priority: Major
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> - activemq.notifications are being transferred to the target node, unless an
> ignore is setup
> - topics are being duplicated after redistribution
> - topics sends are being duplicated when a 2 node cluster mirrors to another
> 2 node cluster, and both nodes are mirrored.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARTEMIS-4252) Fix flaky QuorumFailOverTest tests
Domenico Francesco Bruscino created ARTEMIS-4252: Summary: Fix flaky QuorumFailOverTest tests Key: ARTEMIS-4252 URL: https://issues.apache.org/jira/browse/ARTEMIS-4252 Project: ActiveMQ Artemis Issue Type: Test Reporter: Domenico Francesco Bruscino Assignee: Domenico Francesco Bruscino QuorumFailOverTest tests are intermittently failing. To fix QuorumFailOverTest tests, we should wait for cluster bridge connections. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work logged] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?focusedWorklogId=858670=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858670 ] ASF GitHub Bot logged work on ARTEMIS-4251: --- Author: ASF GitHub Bot Created on: 24/Apr/23 07:56 Start Date: 24/Apr/23 07:56 Worklog Time Spent: 10m Work Description: brusdev opened a new pull request, #4447: URL: https://github.com/apache/activemq-artemis/pull/4447 Improve the CORE client failover connecting to other live servers when all reconnect attempts fails, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client should reconnect its sessions to the other liver broker. Issue Time Tracking --- Worklog Id: (was: 858670) Remaining Estimate: 0h Time Spent: 10m > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers when all reconnect attempts fails, i.e. in a cluster composed of 2 > live servers, when the server to which the CORE client is connected goes down > the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4251: - Description: The CORE clients support failover only reconnecting to the current live/backup pair. Improve the CORE client failover connecting to other live servers when all reconnect attempts fails, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client should reconnect its sessions to the other liver broker. (was: The CORE clients support failover only reconnecting to the current live/backup pair. Improve the CORE client failover connecting to other live servers too when all reconnect attempts fails, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client should reconnect its sessions to the other liver broker.) > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers when all reconnect attempts fails, i.e. in a cluster composed of 2 > live servers, when the server to which the CORE client is connected goes down > the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4251: - Description: The CORE clients support failover only reconnecting to the current live/backup pair. Improve the CORE client failover connecting to other live servers too when all reconnect attempts fails, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client should reconnect its sessions to the other liver broker. (was: The CORE clients support failover only reconnecting to the current live/backup pair. Improve the CORE client failover using other live servers too, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client could reconnect its sessions to the other liver broker.) > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover connecting to other live > servers too when all reconnect attempts fails, i.e. in a cluster composed of > 2 live servers, when the server to which the CORE client is connected goes > down the CORE client should reconnect its sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4251) Support CORE client failover to other live servers
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4251: - Summary: Support CORE client failover to other live servers (was: Support CORE client failover without HA) > Support CORE client failover to other live servers > -- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover using other live servers > too, i.e. in a cluster composed of 2 live servers, when the server to which > the CORE client is connected goes down the CORE client could reconnect its > sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4251) Support CORE client failover without HA
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4251: - Description: The CORE clients support failover only reconnecting to the current live/backup pair. Improve the CORE client failover using other live servers too, i.e. in a cluster composed of 2 live servers, when the server to which the CORE client is connected goes down the CORE client could reconnect its sessions to the other liver broker. > Support CORE client failover without HA > --- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > > The CORE clients support failover only reconnecting to the current > live/backup pair. Improve the CORE client failover using other live servers > too, i.e. in a cluster composed of 2 live servers, when the server to which > the CORE client is connected goes down the CORE client could reconnect its > sessions to the other liver broker. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4251) Support CORE clientfailover without HA
Domenico Francesco Bruscino created ARTEMIS-4251: Summary: Support CORE clientfailover without HA Key: ARTEMIS-4251 URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 Project: ActiveMQ Artemis Issue Type: Improvement Reporter: Domenico Francesco Bruscino Assignee: Domenico Francesco Bruscino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4251) Support CORE client failover without HA
[ https://issues.apache.org/jira/browse/ARTEMIS-4251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Domenico Francesco Bruscino updated ARTEMIS-4251: - Summary: Support CORE client failover without HA (was: Support CORE clientfailover without HA) > Support CORE client failover without HA > --- > > Key: ARTEMIS-4251 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4251 > Project: ActiveMQ Artemis > Issue Type: Improvement >Reporter: Domenico Francesco Bruscino >Assignee: Domenico Francesco Bruscino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
