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

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

Github user ted-ross commented on a diff in the pull request:

    https://github.com/apache/qpid-dispatch/pull/149#discussion_r107224807
  
    --- Diff: src/router_core/connections.c ---
    @@ -1297,6 +1320,7 @@ static void 
qdr_link_inbound_first_attach_CT(qdr_core_t *core, qdr_action_t *act
                         //
                         // This is a link-routed destination, forward the 
attach to the next hop
                         //
    +                    set_terminus_address(link, dir);
    --- End diff --
    
    You are calling a non-CT function from within a CT function.  The non-CT 
function accesses pn_link_t structures that are unsafe to access from a thread 
that is not the IO thread that owns the connection on which the link flows.  
This is very likely to cause memory corruption and crashes.


> Address field is empty for link routed links in the qdstat "links" output
> -------------------------------------------------------------------------
>
>                 Key: DISPATCH-357
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-357
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Paolo Patierno
>            Assignee: Ganesh Murthy
>             Fix For: 0.8.0
>
>         Attachments: qdstat_links.txt
>
>
> I have a router with a link routed link for address "my_queue" configured (in 
> both directions in and out).
> Executing "qdstat -l", it doesn't show me the address name; the "addr" field 
> is empty.
> Attached you can find the file with output.



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

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

Reply via email to