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

ASF GitHub Bot logged work on ARTEMIS-3243:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Jul/21 22:17
            Start Date: 07/Jul/21 22:17
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic commented on a change in pull request 
#3633:
URL: https://github.com/apache/activemq-artemis/pull/3633#discussion_r665741077



##########
File path: 
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/broker/AMQPMessage.java
##########
@@ -1062,6 +1062,9 @@ public final Object getDuplicateProperty() {
 
    @Override
    public boolean isDurable() {
+      if (!isLargeMessage()) {
+         ensureMessageDataScanned();
+      }

Review comment:
       @gemmellr right.. that's what I'm aiming to.. some sort of scan header..
   
   The fix I have in place is just so I can continue in other changes before I 
can come back into this one.
   
   I will probably need to raise another JIRA on this one.. as it seems a bug 
to me.




-- 
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-unsubscr...@activemq.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

    Worklog Id:     (was: 620250)
    Time Spent: 19.5h  (was: 19h 20m)

> Enhance AMQP Mirror support with dual mirror
> --------------------------------------------
>
>                 Key: ARTEMIS-3243
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3243
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.17.0
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>             Fix For: 2.18.0
>
>          Time Spent: 19.5h
>  Remaining Estimate: 0h
>
> at the current Mirror version, we can only mirror into a single direction.
> With this enhancement the two (or more brokers) would be connected to each 
> other, each one having its own ID, and each one would send updates to the 
> other broker.
> The outcome is that if you just transferred producers and consumers from one 
> broker into the other, the fallback would be automatic and simple. No need to 
> disable and enable mirror options.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to