[
https://issues.apache.org/jira/browse/PROTON-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504801#comment-14504801
]
ASF GitHub Bot commented on PROTON-853:
---------------------------------------
Github user rhs commented on the pull request:
https://github.com/apache/qpid-proton/pull/21#issuecomment-94755563
+1 from me
Initially I thought this wouldn't account for detach properly, but looking
at the code I managed to convince myself that it will. If you have time,
however, it would be nice to augment/add a test of the detach scenario.
> [proton-j] the transport emitted a new link attach for a link in the process
> of being detached
> ----------------------------------------------------------------------------------------------
>
> 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
>
> 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)
