[
https://issues.apache.org/jira/browse/QPID-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218382#comment-16218382
]
Lorenz Quack commented on QPID-7954:
------------------------------------
It also looks like that if we do a broker initiated link detach we immediately
discard the endpoint from the session. So if the remote side sends another
performative (or it is already on the wire) involving the handle it will result
in a {{unattached-handle}} session error.
We should only discard the input handle once we receive the detach from the
remote peer or after a timeout.
> [Java Broker, AMQP 1.0] Improve AMQP 1.0 detach code
> ----------------------------------------------------
>
> Key: QPID-7954
> URL: https://issues.apache.org/jira/browse/QPID-7954
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: Future
>
>
> Currently the AMQP detach handling code is messy.
> It could use a good refactoring and cleanup.
> Also the following issues need looking into:
> * Are we handling simultaneous detach correctly? There seems to be shared
> code between broker- and client-side detach ({{Session_1_0#detach()}}) which
> unmaps both the input and output handle.
> * We should probably have a ticker timing out clients that do not send back a
> detach after a broker side detach in a reasonable amount of time.
> * Are all state transitions handled correctly?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
