You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/06/18 22:53:01 UTC

[jira] [Resolved] (QPID-6599) Attempting to actively declare a reserved exchange causes existing exchange to be partially removed from the in memory model

     [ https://issues.apache.org/jira/browse/QPID-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey resolved QPID-6599.
-------------------------------
    Resolution: Fixed

> 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
>    Affects Versions: 0.30, 0.32
>            Reporter: Keith Wall
>            Assignee: Rob Godfrey
>             Fix For: 6.0 [Java]
>
>
> 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 exchange 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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org