[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511213#comment-14511213
]
ASF subversion and git services commented on PROTON-850:
--------------------------------------------------------
Commit acd1e1c9a582aaf190bb32ebc5bd9e590bd71930 in qpid-proton's branch
refs/heads/0.9.x from Robert Gemmell
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=acd1e1c ]
PROTON-853: add a test that catches the issue from PROTON-154 (and PROTON-850)
(cherry picked from commit 252f5f0c1a3cb50edac7813eb233a37697e1f2ab)
> 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
> Assignee: Gordon Sim
> Fix For: 0.10
>
> 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)
