[
https://issues.apache.org/jira/browse/QPID-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771567#action_12771567
]
Gordon Sim commented on QPID-2167:
----------------------------------
That is actually expected behaviour. The amqp spec dictates that the session is
destroyed with a not-found 'exception'. The c++ client will throw the exception
that destroyed the session on any subsequent call.
If you want to test that a queue exists without destroying your session you can
use queueQuery() or exchangeBound() (the latter is preferable where the queue
may have a lot of messages due to a currently suboptimal impl of queueQuery()).
> 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]
