[
https://issues.apache.org/jira/browse/QPID-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192393#comment-13192393
]
Jason Dillaman commented on QPID-3777:
--------------------------------------
I can see your point with regard to the client library changes. It would be
trivial in our use case to have the client application append a new argument to
indicate that the binding should be scoped w/ the session.
In regards to the broker side tuple which stores the user id and url, my
original implementation did not attempt to store the data. However, I was
forced to store the data after discovering that 'SessionState::getConnection'
would throw an assertion failure while ExchangeHandlerImpl's destructor was
attempting to cleanup the bindings.
> Messaging API link binding is not unbound if client disconnects uncleanly
> -------------------------------------------------------------------------
>
> Key: QPID-3777
> URL: https://issues.apache.org/jira/browse/QPID-3777
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Affects Versions: 0.12
> Reporter: Jason Dillaman
> Priority: Minor
> Attachments: QPID-3777.patch
>
>
> Description of problem:
> Link bindings within the Messaging API (e.g. 'test.q;{create:always,
> node:{type:queue},link:{x-bindings:[{exchange:test.ex,queue:test.q,key:#}]}}')
> are implemented solely within the client. Therefore, if the connection
> between the broker and the client is severed, the client will not be able to
> remove the link binding as it normally would during a clean client disconnect.
> How reproducible:
> 100%
> Steps to Reproduce:
> 1. Create a link binding via a C++ Messaging API sender or receiver
> 2. Kill the client or sever the link between the client and broker
>
> Actual results:
> The link binding is still present in the broker
> Expected results:
> The link binding would be unbound when the broker discovers the client was
> disconnected
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
