[
https://issues.apache.org/jira/browse/DISPATCH-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-158:
------------------------------
Fix Version/s: (was: 0.6)
> Dispatch should ignore frames after receiving close frame
> ---------------------------------------------------------
>
> Key: DISPATCH-158
> URL: https://issues.apache.org/jira/browse/DISPATCH-158
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 0.4
> Reporter: Pavel Moravec
> Priority: Minor
>
> (not sure if component matches, or if the bug isn't in proton, please change
> accordingly)
> Having a client / mobile subscriber receiving messages that suddenly closes
> the AMQP1.0 connection by sending "close" performative, the dispatch has to
> ignore any further performatives on the connection (ideally raising a
> warning). And it should not forward them further.
> See https://issues.jboss.org/browse/ENTMQCL-14 for an example of
> malfunctioning client that sends close frame followed by flow frame (against
> AMQP spec). Dispatch then forwards the flow frame (with invalid channel
> number 65534 and invalid handle 4294967294) before closing the AMQP
> connection. This flow should not be forwarded but ignored - dont propagate
> misbehaviour in AMQP 1.0 communication.
> (dispatch router does not violate AMQP1.0 spec, "just" reacts on such
> violation by sending wrong and ridiculous flow frame)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
