[QPID-7375] [Java Client] [BURL] Client should not actively declare custom exchanges and queues by default

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: Future
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Keith Wall
• Created: 03/Aug/16 11:05
• Updated: 30/Jan/18 17:22
• Resolved: 30/Jan/18 17:22

Description

The legacy Qpid JMS client, when BURL addressing is in use, will by default:

• actively declare custom exchanges (i.e. thoses not prefixed by amqp.) on publish
• actively declare custom exchanges and queues on the consume path.

This behaviour is longstanding, but causes problems when ACLs are in use with the Qpid Broker for Java (see QPID-7370).

The following changes are required:

• When creating a publisher and ADDRs are not in use, the exchange should be passively declared.
• When creating a consumer and ADDRs are not in use, the exchange and queue should both be passively declared. There will be an option to allow the queue to be declared actively if the old behaviour is required.

In general, users will be directed to create queues and exchanges through management rather than relying on the publisher/consumer side effects, as this is more in keeping with the direction of AMQP 1.0.

Issue Links

• relates to: QPID-7370 Broker now rejects custom active exchange declaration when exchange already exists and ACLs are in use