[
https://issues.apache.org/jira/browse/QPID-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-6599:
-----------------------------
Description:
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.
was:
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.
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.
> 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: [email protected]
For additional commands, e-mail: [email protected]
