[DISPATCH-640] containerId field conflics with the connector name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.0
• Fix Version/s: 0.8.0
• Component/s: Router Node

Environment

rhel6x,i rhel7x

• Assignee: Ganesh Murthy
• Reporter: Matej Lesko
• Created: 23/Feb/17 17:34
• Updated: 02/Oct/19 17:55
• Resolved: 01/Mar/17 18:08

Description

Using this configuration with the JAMQ7 (with container_id "dtest") a problem appears when a name is specified for the connector.
In this case linkRoutes are not established to the broker.
Commenting out a name attribute in connector entity linkRouting works as expected.

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
}

Issue Links

• links to: GitHub Pull Request #144