[DISPATCH-641] Make containerId attribute work with clients

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.7.0
• Fix Version/s: 0.8.0
• Component/s: Router Node
• Assignee: Ganesh Murthy
• Reporter: Matej Lesko
• Created: 23/Feb/17 18:09
• Updated: 20/Nov/17 18:35
• Resolved: 01/Mar/17 15:34

Description

During verification of issue https://issues.apache.org/jira/browse/DISPATCH-628
I found out that when I set this containerId in the clients, router can see it but it can not route it.

E.g. I have sender with the containerId "xxx" and autoLink entity with the containerId "xxx" ->
this autoLink does not activate in this scenario.

Simply said when I have sender/receiver with the containerId set and matching the containerId attribute in the configuration file, it does
not accept the connection. e.g. linkRoute usage ends with the "Link error: No route to the destination node".

Possible configuration to use(same applies for autoLink entities)

router {
    mode: standalone
    id: Router.A
}

listener {
    host: 0.0.0.0
    port: amqp
    authenticatePeer: no
    saslMechanisms: ANONYMOUS
}

connector {
    name: broker
    host: MY-HOST
    role: route-container
    port: amqp
}

address {
    prefix: jms.queue
    waypoint: yes
    distribution: balanced
}

linkRoute {
    name: myqueueIn
    dir: in
    prefix: jms.queue.myqueue
    connection: broker
    containerId: dtest
}

linkRoute {
    name: myqueueOut
    dir: out
    prefix: jms.queue.myqueue
    connection: broker
    containerId: dtest
}

log {
    module: MESSAGE
    enable: debug
    timestamp: yes
}

Right now, router works only as described e.g. here https://issues.apache.org/jira/browse/DISPATCH-640

In such a case, it is important to set a name (aka container_id) for the broker, matching the value of containerId attribute of the chosen linkRoute/autoLink entity. Then all messages are routed to this broker, ignoring the value of container_id of the actual client itself.

Request is that this value would be used to "specify" which clients would actually be allowed to make a connection to the broker.

Usages:
Scenario A:
1. Client has containerId=xxx, address="myqueue"
2. linkRoute has containerId=yyy, prefix="myqueue"
resolution: connection won't be established, not matching containerId

Scenario B:
1. Client has containerId=xxx, address="myqueue"
2. linkRoute has containerId=xxx, prefix="myqueue"
resolution: connection will be established, client sends messages to the broker

As described in https://issues.apache.org/jira/browse/DISPATCH-639 ->
"if there is a container field, use it otherwise use the connection_field to specify the connection to use."

This could be elevated to the use case, where an condition as:
"if there is container field and also connection_field specified, demand matching containerId from the client"

Issue Links

• is related to: DISPATCH-639 Document proper usage of containerId for autoLinks/linkRoutes entities