[ARTEMIS-2032] Artemis RA connections disconnected after failover

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.3, 2.7.0
• Assignee: Unassigned
• Reporter: Martyn Taylor
• Created: 14/Aug/18 16:13
• Updated: 20/Aug/18 16:57
• Resolved: 20/Aug/18 16:57

Description

This was tested within the WF application server.  It was discovered that the RA does note fail over from live to backup under certain scenarios: 

Backup activates after a fail over, the RA does not reconnect to that backup.

Test scenario:

These tests are using the Artemis RA within the WF application server.

• There are three servers. Live server (Node 1) and backup server (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.

Issue Links

• duplicates: ARTEMIS-2030 Interrupting Threads on the ResourceAdapter may lead to unexpected issues
• links to: WFWIP-65