qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-640) containerId field conflics with the connector name
Date Mon, 27 Feb 2017 19:28:45 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886364#comment-15886364
] 

ASF GitHub Bot commented on DISPATCH-640:
-----------------------------------------

GitHub user ganeshmurthy opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/144

    DISPATCH-640 - Added code to enable the same connection object to be …

    …obtained using a containerId and a connectionId

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-640

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-dispatch/pull/144.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #144
    
----
commit 04c5bbe480b8447111cebf37086f8e0646dfb89e
Author: Ganesh Murthy <gmurthy@redhat.com>
Date:   2017-02-27T14:55:22Z

    DISPATCH-640 - Added code to enable the same connection object to be obtained using a
containerId and a connectionId

----


> containerId field conflics with the connector name
> --------------------------------------------------
>
>                 Key: DISPATCH-640
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-640
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 0.7.0
>         Environment: rhel6x,i rhel7x
>            Reporter: Matej Lesko
>            Assignee: Ganesh Murthy
>
> 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.

> {noformat}
> 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
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message