Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
AMQ 7.8.0.GA
-
None
-
False
-
False
-
Undefined
-
Description
AMQ Broker 7.8 Managed using Operator 0.18, the queue is present on both broker-0 and broker-1 before scaledown test.
Messages are sent to broker-1 and then the broker-1 is scaled down.
Drainer pod run and find messages to be migrated on broker-0.
At the end of scale down procedure the messages are not present on broker-0 and the following trace is reported on broker-0 log:
020-12-10 13:17:49,681 WARN [org.apache.activemq.artemis.core.server] AMQ222196: Could not find binding with id=363,965 on routeFromCluster for message=CoreMessage[messageID=36507634086,durable=true,userID=null,priority=5, timestamp=Thu Dec 10 13:16:28 UTC 2020,expiration=0, durable=true, address=rbbhDMS,size=819,properties=TypedProperties[Source=email,FaxNumber=033665665,JMS_AMQP_ORIGINAL_ENCODING=5,Status=1,Creator=User1,Urgency=0,MailFrom=from@dddd,JMS_AMQP_HEADER=true,PaymentType=0,Agency=000291,DocumentumID=UPP-57500-25,JMS_AMQP_HEADERPRIORITY=true,DateCreated=12/10/2020 13:16:28,JMS_AMQP_HEADERDURABLE=true,DMSMQID=1]]@762452523 binding = BindingsImpl [name=rbbhDMS]
Broker-0 log in attach.ex-aao-ss-0_logs.txt