[
https://issues.apache.org/jira/browse/QPID-7370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15399396#comment-15399396
]
Keith Wall edited comment on QPID-7370 at 7/29/16 3:15 PM:
-----------------------------------------------------------
Suggestion is that we change {{AMQChannel#receiveExchangeDeclare}} so that if
the peer is a client known to send active declares in this way, the if the
AccessControlException occurs AND the exchange exists and it of the same type,
send an {{ExchangeDeclareOk}}, otherwise continue to reject the exchange
declare in the way we do today.
Queue declares may need to be similarly changed.
How do we want to change the client?
was (Author: k-wall):
Suggestion is that we change {{AMQChannel#receiveExchangeDeclare}} so that if
the peer is a client known to send active declares in this way, the if the
AccessControlException occurs AND the exchange exists and it of the same type,
send an {{ExchangeDeclareOk}}, otherwise continue to reject the exchange
declare in the way we do today.
Queue declares may need to be similarly changed.
> Broker now rejects custom active exchange declaration when exchange already
> exists and ACLs are in use
> ------------------------------------------------------------------------------------------------------
>
> Key: QPID-7370
> URL: https://issues.apache.org/jira/browse/QPID-7370
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.24, 0.26, 0.28, 0.30, 0.32, qpid-java-6.0,
> qpid-java-6.0.4
> Reporter: Keith Wall
>
> The default behaviour of the Qpid JMS Client 0.8..0-91 when BURLs are in use
> is to _actively_ declare custom exchanges (i..e those not named {{amq.}} on
> the publish code path before sending a message to that exchange.
> At 0.24 in the Broker, the behaviour of {{ExchnageDeclareHandler}} (now
> {{AMQChannel#receiveExchangeDeclare}} was changed so that so that such
> declares may be rejected by the ACL system even if the exchange already
> exists and is of the correct type. Earlier versions of the Broker permitted
> such declares, providing type etc matched.
> It is felt that the new behaviour is superior to the old, but this creates a
> compatibility problem for users upgrading from older versions of the Broker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
