You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2015/04/16 20:28:58 UTC

[jira] [Issue Comment Deleted] (PROTON-850) inconsistent state when reusing link name

     [ https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim updated PROTON-850:
------------------------------
    Comment: was deleted

(was: Actually, this is not really a bug as described. The local state *is* closed. If the link is freed before the second attach comes in, a new link object is created. However if not, the original link appears to get used and even if you then open it again, the attach is not sent out.)

> inconsistent state when reusing link name
> -----------------------------------------
>
>                 Key: PROTON-850
>                 URL: https://issues.apache.org/jira/browse/PROTON-850
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c, python-binding
>    Affects Versions: 0.9
>            Reporter: Gordon Sim
>         Attachments: PROTON_850.py
>
>
> If a link is closed, and a new link with the same name is created and opened, the attach received for the second link from the peer is applied to the old link.
> If the old link is freed after being closed, this is avoided, but I'm not sure that is possible via e.g. the python bindings.
> The root of the problem I think is that a handle is reused after the link is closed, whether freed or not, but when processing an incoming attach, it is the link name that is used to find the appropriate link, which iterates through all links until it matches one by name, which in this case is the old, closed link.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)