Sometimes happens there are undelivered messages in scenario with servers in remote JCA topology are restarted. The problem is that messages are not redistributed to node with consumer because Artemis cluster was not formed restart. Issue is very intermittent and hard to hit especially with enabled traces.
Impact for the customer: Restarted node in Artemis cluster might not join cluster again. Server(s) in cluster must be restarted so cluster is formed correctly.
Test scenario:
- Start 2 server in Artemis cluster
- Start 2 servers with MDB connected to Artemis cluster
- MDB resends messages from InQueue to OutQueue from/to remote cluster
- Send messages to InQueue
- Restart all server (one by one)
- Consumes messages from OutQueue
Results:
After the test there are undelivered messages.
This issue is regression against EAP 7.1 and EAP 7.2.0.CD13.
- clones
-
WFLY-11029 Sometimes Artemis cluster with JGroups discovery is not formed after restart
- Reopened
- is cloned by
-
JBEAP-18324 (7.3.z) ENTMQBR-2049 - Sometimes Artemis cluster with JGroups discovery is not formed after restart
- Closed
-
ENTMQBR-2049 Sometimes Artemis cluster with JGroups discovery is not formed after restart
- Closed