[
https://issues.apache.org/jira/browse/QPID-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592086#comment-14592086
]
ASF subversion and git services commented on QPID-6599:
-------------------------------------------------------
Commit 1686269 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1686269 ]
QPID-6599: [Python Tests AMQP 0-8] Supporting test for Java Broker Defect
> Attempting to actively declare a reserved exchange causes existing exchange
> to be partially removed from the in memory model
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-6599
> URL: https://issues.apache.org/jira/browse/QPID-6599
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: 0.30, 0.32
>
>
> If I try to actively declare a reserved exchange (amq.direct for instance),
> the Broker correctly detects that the attempt to create an exchange with the
> prefix "amp." is disallowed AbstractExchange#onValidate, but then goes on to
> erroneously unlink the existing existing from the in memory model. Clients
> then see 404 "Unknown exchange: 'amq.direct'". Restarting the Broker works
> around the problem.
> This problem cannot occur when using recent versions of the Qpid Java Client
> (which always send reserved exchange declares as passive). It came to light
> as a user was using a Qpid Java client circa 2008 (~0.6) which did not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
