qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Sim (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-3242) Unexplained behaviour when assertions and auto-delete are combined
Date Mon, 09 May 2011 16:00:03 GMT

    [ https://issues.apache.org/jira/browse/QPID-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030781#comment-13030781

Gordon Sim commented on QPID-3242:

On first resolution (when the queue is in fact created), the address resolution cache is populated.
The next time that queue is referenced (in this case in the address with an assertion) it
uses the cached resolution status and then goes on to subscribe to that queue. However the
queue doesn't exist so the subscription results in the session being invalidated.

This issue is not a bug. However I have raised another issue regarding the potential of the
cache to become stale and lead to initially unintuitive behaviour:

> 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

View raw message