Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: AMQ 7.0.2.GA
Affects Version/s: None
Component/s: None
Labels:
- internal
- replication
Environment:

Hide

– Consumers:
Tests are made with Tsung with 20 consumers instances running a python client , with 2 process and 20 threads each. All messages that will be consumed were persisted. Connections aren't persisted and clients doesn't use transactions. Python uses AMQP to connect to Artemis.

– Producers:
Camel JMS Bridge consuming from MQ Series and producing to A-MQ7

Show
– Consumers: Tests are made with Tsung with 20 consumers instances running a python client , with 2 process and 20 threads each. All messages that will be consumed were persisted. Connections aren't persisted and clients doesn't use transactions. Python uses AMQP to connect to Artemis. – Producers: Camel JMS Bridge consuming from MQ Series and producing to A-MQ7

GSS Priority:
Target Release:

AMQ 7.0.2.GA
Steps to Reproduce:

Hide

With a Master x Slave pair similar from artemis examples, follow the steps below:

1. Start master broker
2. JMS Producers will be sending messages to A-MQ 7
3. AMQP Consumers will be consuming messages from A-MQ 7
4. Start slave broker

master and slave try to synchronize the replication, after a while slave aborts and stops with logs below:
12:08:53,368 WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped

Show
With a Master x Slave pair similar from artemis examples, follow the steps below: 1. Start master broker 2. JMS Producers will be sending messages to A-MQ 7 3. AMQP Consumers will be consuming messages from A-MQ 7 4. Start slave broker master and slave try to synchronize the replication, after a while slave aborts and stops with logs below: 12:08:53,368 WARN [org.apache.activemq.artemis.core.server] AMQ222040: Server is stopped

while master is under load and a slave is started sync won't catch up.
after a while, slave shuts down
it highly impacts production environment

is incorporated by

JBEAP-8630 (7.0.z) The backup server is not responding promptly introducing latency beyond the limit.

is related to

JBEAP-7968 (7.1.0) The backup server is not responding promptly introducing latency beyond the limit.