[
https://issues.apache.org/jira/browse/PROTON-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512671#comment-14512671
]
ASF subversion and git services commented on PROTON-853:
--------------------------------------------------------
Commit 77c1ee076ae4a4bcbec850572deb276ebd0b8c7b 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=77c1ee0 ]
PROTON-853: dont return the cached links if they are already in the closed
state, instead create a new object and ensure the old links also get freed.
Also fixes similar behaviour as in PROTON-850.
This closes #21
(cherry picked from commit f2d7d669155a2ca57606c9381f4f1720739be79b)
> [proton-j] the transport emitted a new attach frame for a link in the process
> of being closed
> ---------------------------------------------------------------------------------------------
>
> Key: PROTON-853
> URL: https://issues.apache.org/jira/browse/PROTON-853
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.9
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.10
>
>
> When upgrading to use 0.9 for the JMS client, we see some NPEs on the client
> as it tries processing the events being emitted by the connection. This was
> due to multiple link attach and detach frames arriving in the for the same
> consumer link.
> What appears to be happening is that while closing the consumer, after the
> client emits its detach frame proton then emits a new attach frame for the
> link, before the server responds to the original detach, even though the
> client made no attempt to recreate the consumer. It looks like the clients
> handling of a flow frame which arrived after it emitted the original detach
> meant that the link was modified, and the transport reacted by sending out a
> new attach. This appears to be due to a change made in 0.9 for PROTON-154.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
