[
https://issues.apache.org/jira/browse/PROTON-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882943#comment-13882943
]
Rafael H. Schloming commented on PROTON-496:
--------------------------------------------
I don't think it's being a bad citizen to leave as is. The spec explicitly
defines all session state to be scoped to connections just so you don't have to
worry about cleaning them up if you don't want to. Likewise for session scoped
links. Part of the point of this is to be able to support low overhead
connection setup/teardown scenarios, as well as simply to ensure robustness,
e.g. don't leave session state lying around for connections that have gone away.
I don't mind the fix if there is a specific interop issue, but if that is the
case then we should also push back and file a bug with the non conformant
implementation. If there is no interop issue then I think the change just adds
extra wire overhead for no reason.
> [Messenger] Messenger fails to send "end" on shutdown.
> ------------------------------------------------------
>
> Key: PROTON-496
> URL: https://issues.apache.org/jira/browse/PROTON-496
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: 0.6
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Trivial
> Fix For: 0.7
>
>
> $ export PN_TRACE_FRM=1
> $ proton-c/examples/messenger/c/send
> Connected to 0.0.0.0:5672
> [0x151a020]: -> SASL
> [0x151a020]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b""]
> [0x151a020]: <- SASL
> <SNIP>
> [0x151a020]:0 -> @detach(22) [handle=0, closed=true]
> [0x151a020]:0 -> @close(24) []
> [0x151a020]: -> EOS
> [0x151a020]:0 <- @detach(22) [handle=0, closed=true]
> [0x151a020]:0 <- @close(24) []
> [0x151a020]: <- EOS
> Closed 0.0.0.0:5672
> There should be an "@end" frame in there, no?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
