[
https://issues.apache.org/jira/browse/QPID-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771726#action_12771726
]
James Birdsall commented on QPID-2167:
--------------------------------------
Trying to check whether an exchange exists, actually.
It looks like this is expected behavior for declare(passive=true), yes, based
on page 217 of the AMQP 0-10 spec. Sorry about the false alarm there.
However, exchange.query, on page 219, is not documented as raising a not-found
exception -- it's not documented as raising any exceptions at all. It does
have a "not-found" field in the return structure, though, and there's a
getNotExists() method on the return type for session.queryExchange() in the
Qpid C++ client. Am I missing something?
> Attempting to query or declare(passive=true) a nonexistent exchange renders
> session unusable
> --------------------------------------------------------------------------------------------
>
> Key: QPID-2167
> URL: https://issues.apache.org/jira/browse/QPID-2167
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.6
> Environment: Windows Server 2008
> Reporter: James Birdsall
> Fix For: 0.6
>
>
> In a program using the C++ client, running against the C++ broker, trying to
> do a session.exchangeQuery or session.exchangeDeclare (with passive=true) on
> a nonexistent exchange throws a not-found exception. Thereafter, any other
> operations on the same session throw the same exception again, including
> trying to close the session.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
