[
https://issues.apache.org/jira/browse/QPID-7530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7530:
-----------------------------
Fix Version/s: (was: qpid-java-broker-7.0.0)
qpid-java-client-0-x-6.3.0
> [Java Client] AMQSession_0_8#isQueueExist contains dead code intending to
> send passive queue declaration when queue is bound to a default exchange and
> assert flag is set to true
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7530
> URL: https://issues.apache.org/jira/browse/QPID-7530
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: qpid-java-6.1
> Reporter: Alex Rudyy
> Assignee: Keith Wall
> Priority: Trivial
> Fix For: qpid-java-client-0-x-6.3.0
>
>
> AMQSession_0_8#isQueueExist contains dead code creating FailoverNoopSupport
> for sending queue declare command which never executed. The code was added
> when support for address based destinations on 0.8 path was introduced.
> The callback is created when ExchangeBound for default exchange returns
> positive reply and assert parameter is set to true. The passive queue
> creation flag is set in FailoverNoopSupport. Execution of FailoverNoopSupport
> sending passive queue declare for non-existing queue would cause session
> close by the broker. It seems that passive queue declaration can only fail
> when queue is deleted between sending of ExchangeBound and QueueDeclare.
> Apart from this corner case, the sending of passive queue declare should be
> successful and client should continue performing its work after receiving of
> QueueDeclareOk
> It seems that FailoverNoopSupport should be allowed to execute
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
