[jira] [Commented] (DISPATCH-802) refuse transaction coordination links if they can't be routed to a coordinator

["Ganesh Murthy (JIRA)" <ji...@apache.org>]

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

Ganesh Murthy commented on DISPATCH-802:
----------------------------------------

[~tross@redhat.com] thinks that just adding the following link route to the default config file should be a sufficient enough solution to this problem 

{noformat}
linkRoute {
    prefix: $coordinator
    dir: in
    connection: broker
}
{noformat}

> refuse transaction coordination links if they can't be routed to a coordinator
> ------------------------------------------------------------------------------
>
>                 Key: DISPATCH-802
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-802
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: Robbie Gemmell
>            Assignee: Ganesh Murthy
>
> The router is accepting transaction coordinator links even if the support from DISPATCH-195 is not being used to link-route them somewhere that can handle coordination. If the router can't link-route to a coordinator, and knows it can't coordinate transactions itself, it shouldn't accept the links to begin with but rather refuse them so clients know they will never work and why.
> Prior to 0.8.0, credit was also given on these links, allowing attempt to declare transactions. From 0.8.0 no credit is given since there is no receiver, so clients have no way to use the accepted link and no indication why.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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