[QPID-7370] Broker now rejects custom active exchange declaration when exchange already exists and ACLs are in use

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 0.24, 0.26, 0.28, 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.4
• Component/s: Broker-J
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 29/Jul/16 14:08
• Updated: 03/Aug/16 11:06
• Resolved: 03/Aug/16 10:52

Description

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.

Issue Links

• is related to: QPID-7375 [Java Client] [BURL] Client should not actively declare custom exchanges and queues by default