[QPID-5816] [Java Client 0-10] If a resolved destination is used to create a consumer on a new connection created after destination was resolved, the client does not try to create the destination on the broker

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20, 0.22, 0.24, 0.26
• Fix Version/s: qpid-java-6.0.3, qpid-java-6.1
• Component/s: JMS AMQP 0-x
• Assignee: Unassigned
• Reporter: Alex Rudyy
• Created: 13/Jun/14 16:33
• Updated: 02/Oct/19 19:20
• Resolved: 12/May/16 08:42

Description

On consumer creation for a destination marked as resolved 0.10 client does not send exchange.declare, queue.declare and exchange.bind commands to the broker in order to create the corresponding broker entities.

If such resolved destination is used to create consumer and the destination node does not exist on a broker, the consumer creation will fail.

In response to subscribe command the broker can return an exception because destination does not exist:

...
SEND: [conn:7e779b1b] ch=0 id=2 MessageSubscribe(queue=test_queue, destination=1, acceptMode=EXPLICIT, acquireMode=PRE_ACQUIRED, resumeTtl=0, arguments={x-filter-jms-selector=})
...
RECV: [conn:7e779b1b] ch=0 ExecutionException(errorCode=NOT_FOUND, commandId=2, description=Queue: test_queue not found)
...

Issue Links

• is related to: QPID-6300 Fail to reconnect after qpid shutdown and restart, for an auto-delete queue