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

ASF GitHub Bot logged work on AMQ-8354:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Jan/23 08:10
            Start Date: 11/Jan/23 08:10
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on code in PR #953:
URL: https://github.com/apache/activemq/pull/953#discussion_r1066683378


##########
activemq-broker/src/main/java/org/apache/activemq/broker/scheduler/SchedulerBroker.java:
##########
@@ -54,7 +54,7 @@
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
 
-public class SchedulerBroker extends BrokerFilter implements JobListener {
+public class SchedulerBroker extends MutableBrokerFilter implements 
JobListener {

Review Comment:
   Wont this be overhead now for use cases not needing this? due to the sync in 
mutable thats needed. e.g. this will introduce a perf drop for existing users





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

    Worklog Id:     (was: 838533)
    Time Spent: 1h  (was: 50m)

> Asynchronous Disaster Recovery
> ------------------------------
>
>                 Key: AMQ-8354
>                 URL: https://issues.apache.org/jira/browse/AMQ-8354
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Étienne Hossack
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In ActiveMQ Artemis, asynchronous broker replication can be achieved through 
> an AMQP mirror. This provides a strong solution for disaster recovery.
> We do not have such a feature in the ActiveMQ 5.X codebase, and there is 
> great potential to satisfy compliance needs with such a feature.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to