-
Bug
-
Resolution: Done
-
Blocker
There is regression againt Artemis 1.5.5.0012 in scenario with failover of Artemis RA from live to backup (shared store, dedicated topology). After backup activates after failover, connections of RA does not failover to backup (or are disconnected from backup just after failover)
Test scenario:
- There are three servers. Live server (Node 1) and backupserver (Node 2) are in dedicated HA topology.
- InQueue and OutQueue are deployed on live and backup. Send messages to InQueue on live server.
- When all messages are sent, deploy message driven bean on Node 3.
- MDB sends messages form InQueue to OutQueue.
- Shutdown live server. Wait for backup server to alive, then start live server again and stop backup.
- Receive messages from OutQueue from live server.
Results:
After live server is stopped and backup activates, no messages are processed by MDB. Looking at trace logs it seems that MDB does reconnect to backup but it's then disconnected. Then I don't see connector to backup server between tried connectors during reconnection.
Attaching reproduce and logs.
- blocks
-
WFLY-10320 Upgrade artemis from 1.5.x to 2.x.x
- Closed
- is cloned by
-
ENTMQBR-1818 [Artemis 2.x upgrade] Artemis RA connections disconnected after failover
- Closed
- is related to
-
WFLY-11059 Clients do not failover to backup even it if backup started and keep retrying connection
- Resolved