Re-attached conf files with .txt extension.

On Thu, Jul 11, 2019 at 4:36 PM Rabih M <[email protected]> wrote:

> Hello,
>
> We are using Qpid dispatch router 1.7, Qpid broker 7.1.3 on redhat linux
> rhel 6.4.
>
> Use case description:
> We have a cluster of 2 dispatch routers and 2 brokers. A sharded queue
> "myQueue" on the 2 brokers.
> Here is an illustration:
>
> [image: Diagram.jpg]
>
> The producer produces 2 messages, the messages are load balanced on the 2
> brokers. Then, Consumer 1 and consumer 2 ask for a receive().
>
> Our observation is that the consumer 1 consumes the first message and the
> consumer 2 is never getting the second message.
> We are aware that the first dispatch router will do a prefetch for the 2
> messages but what is weird is that the prefetched message 2 is never routed
> to the second dispatch router and consumer 2.
> I attached the dispatch routers config.
>
> Do you have any idea how we can make consumer 2 receive the message?
>
> Thanks for your help,
> Rabih
>
router {
        mode: interior
        id: router2
        workerThreads: 4
        defaultDistribution: unavailable
}

listener {
        name: normal_listener
        host: 0.0.0.0
        port: 5673
        role: normal
        saslMechanisms: ANONYMOUS
        requireSsl: no
        authenticatePeer: no
}

listener {
        name: inter_router_listener
        host: 0.0.0.0
        port: 5683
        role: inter-router
        saslMechanisms: ANONYMOUS
        requireSsl: no
        authenticatePeer: no
}

log {
        module: DEFAULT
        enable: info+
        includeSource: false
        outputFile: stdout
}

connector {
    name: dispatch1
    role: inter-router
    host: 127.0.0.1
    port: 5682
}

connector {
    name: broker1
    role: route-container
    host: 127.0.0.1
    port: 5670
}

connector {
    name: broker2
    role: route-container
    host: 127.0.0.1
    port: 5671
}

address {
    prefix: myQueue
    waypoint: yes
}

autoLink {
    name: consume_myQueue_broker1
    addr: myQueue
    connection: broker1
    direction: in
}

autoLink {
    name: produce_myQueue_broker1
    addr: myQueue
    connection: broker1
    direction: out
}

autoLink {
    name: consume_myQueue_broker2
    addr: myQueue
    connection: broker2
    direction: in
}

autoLink {
    name: produce_myQueue_broker2
    addr: myQueue
    connection: broker2
    direction: out
}
router {
        mode: interior
        id: router1
        workerThreads: 4
        defaultDistribution: unavailable
}

listener {
        name: normal_listener
        host: 0.0.0.0
        port: 5672
        role: normal
        saslMechanisms: ANONYMOUS
        requireSsl: no
        authenticatePeer: no
}

listener {
        name: inter_router_listener
        host: 0.0.0.0
        port: 5682
        role: inter-router
        saslMechanisms: ANONYMOUS
        requireSsl: no
        authenticatePeer: no
}

connector {
    name: broker1
    role: route-container
    host: 127.0.0.1
    port: 5670
    linkCapacity: 1
}

connector {
    name: broker2
    role: route-container
    host: 127.0.0.1
    port: 5671
    linkCapacity: 1
}

address {
    prefix: myQueue
    waypoint: yes
}

autoLink {
    name: consume_myQueue_broker1
    addr: myQueue
    connection: broker1
    direction: in
}

autoLink {
    name: produce_myQueue_broker1
    addr: myQueue
    connection: broker1
    direction: out
}

autoLink {
    name: consume_myQueue_broker2
    addr: myQueue
    connection: broker2
    direction: in
}

autoLink {
    name: produce_myQueue_broker2
    addr: myQueue
    connection: broker2
    direction: out
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to