[DISPATCH-1724] Fallback destination fails when primary consumer is on an auto-link

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.13.0
• Component/s: Router Node
• Assignee: Charles E. Rolke
• Reporter: Ted Ross
• Created: 23/Jul/20 19:13
• Updated: 13/Oct/20 14:09
• Resolved: 07/Aug/20 21:13

Description

Fallback destination is failing for a scenario where it should be working.  In the use case of interest, two message brokers are connected to a single router.  One broker is designated primary and the other secondary.  Both brokers have an instance of the same queue.

The auto-link for enqueue to the primary broker is normal (on phase 0), the auto-link for enqueue to the secondary broker is designated as the fallback.

In this case, if the primary broker is never connected but the secondary broker is, a sender for the address in question is never given credit to send.

Test configuration:

address {
    pattern: FOO
    enableFallback: yes
}

connector {
    host: 127.0.0.1
    port: 10000
    role: route-container
    name: primary
}

connector {
    host: 127.0.0.1
    port: 10001
    role: route-container
    name: secondary
}

autoLink {
    connection: primary
    dir: out
    addr: FOO
}

autoLink {
    connection: secondary
    dir: out
    addr: FOO
    fallback: yes
}