[ARTEMIS-2937] AMQP Server Connectivity

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.16.0
• Component/s: AMQP
• Assignee: Clebert Suconic
• Reporter: Clebert Suconic
• Created: 07/Oct/20 20:13
• Updated: 20/Jan/21 16:26
• Resolved: 03/Nov/20 01:14

Description

This feature adds server side connectivity.

 

It is possible to link two brokers directly using AMQP with this feature, and have a Queue transferring messages to another broker directly. 

 

For this we would have options called <sender and <receiver

 

 

it would also be possible to use qpid-dispatch as an intermediary between clients and the brokers (or eventually between brokers), on that case the option will be <peer

 

it would also be possible to use <mirror with a few option to replicate data between two brokers, bringing the possibility of using it for Disaster & Recovery and Failover.

Issue Links

• is duplicated by: ARTEMIS-30 allow backup servers to service multiple live servers
• is duplicated by: ARTEMIS-31 Disaster recovery
• is related to: ARTEMIS-2977 broker logs huge stacktrace if not supporting any SASL mech offered by remote server
• is related to: ARTEMIS-2967 NPE stack warn logged in AMQPBridgeTest #test testsSimpleConnect()
• is related to: ARTEMIS-2968 stacktrace-including warnings of non-existent queues/addresses emitted during AMQPReplicaTest#testDualStandard
• is related to: ARTEMIS-2969 broker doesnt handle server-connection being severed
• is related to: ARTEMIS-2971 outgoing 'server-connection' doesnt support ANONYMOUS or EXTERNAL SASL mechanisms
• is related to: ARTEMIS-2965 Allow mirror to stop capture events and delete inner queue
• links to: GitHub Pull Request #3294
• links to: GitHub Pull Request #3316
• links to: GitHub Pull Request #3317
• links to: GitHub Pull Request #3319
• links to: GitHub Pull Request #3320
• links to: GitHub Pull Request #3321