You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <ji...@apache.org> on 2011/05/03 20:01:03 UTC
[jira] [Updated] (QPID-3242) Unexplained behaviour when assertions
and auto-delete are combined
[ https://issues.apache.org/jira/browse/QPID-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim updated QPID-3242:
-----------------------------
Attachment: test.py
Test program
> Unexplained behaviour when assertions and auto-delete are combined
> ------------------------------------------------------------------
>
> Key: QPID-3242
> URL: https://issues.apache.org/jira/browse/QPID-3242
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Affects Versions: 0.11
> Reporter: Gordon Sim
> Attachments: test.py
>
>
> Attached test results in a not-found exception on reusing an address that is set to an auto-created queue with server side auto-delete as well as a delete policy set. The assertion step is needed to trigger the issue, but I can't explain the behaviour. May not be a bug per-se, just not obvious why it is doing what it is doing. Appears that second time round the auto-creation is not triggered on sender and so the subscription for the receiver fails. Guessing that it is due to the address resolution cache being used as there does not appear to be another queue/exchange query. However I don't get why the assertion is the triggering of that.
--
This message is automatically generated by JIRA.
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:dev-subscribe@qpid.apache.org