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

ASF subversion and git services commented on DISPATCH-1107:
-----------------------------------------------------------

Commit df7667e8a9fa2ad6a2dd2ca91fe6f4a45b4d4f3c in qpid-dispatch's branch 
refs/heads/master from [~chug]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=df7667e ]

DISPATCH-1107: Add router connection id interrouter Opens

This feature helps disambiguate interrouter connections.
Topology tests generate many connections and resulting logs have the
connection ids. There is nothing topology-specific about this feature.


> Need info for logs to help disambiguate router connections
> ----------------------------------------------------------
>
>                 Key: DISPATCH-1107
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1107
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Router Node
>    Affects Versions: 1.3.0
>            Reporter: Chuck Rolke
>            Priority: Major
>             Fix For: 1.4.0
>
>
> When connections are started by routers to other routers there is no reliable 
> way in the log files for telling the connections apart. Consider a pair of 
> routers where router A creates two connections and sends two Opens to router 
> B. A's log will show that connections [5] and [7] sent the Opens and B's log 
> will show that connections [4] and [6] received and replied to the Opens. But 
> there is no way to know if the connection pairs are '[A-5][B-4] and 
> [A-7][B-6]' or '[A-5][B-6] and [A-7][B-4]'.
> A simple solution to expose this relationship is for the routers to embed the 
> _connid_ in the Open properties. Then the connection relationships between 
> the two routers could be resolved from either router log file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to