[QPID-2809] Once an AMQDestination object resolves an address, it should not try to resolve it again when used in subsequent operations.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7
• Component/s: JMS AMQP 0-x
• Assignee: Rajith Muditha Attapattu
• Reporter: Rajith Muditha Attapattu
• Created: 17/Aug/10 20:44
• Updated: 14/Mar/17 20:08
• Resolved: 18/Oct/10 22:01

Description

Once an AMQDestination object resolves an address, it should not try to resolve it again during subsequent operations.
If the destination is used again to create producers or consumers it should be able to reuse the information already obtained by querying the broker.
This is also a good worksaround for the locking issue mentioned in QPID-2808, as it prevents the code segment that causes the locking being executed during the failover operation.

However the following needs to be considered.

Consider the address "amq.topic/foo" vs "amq.topic/foo; { link {name: my-foo-queue}}"
If we create two destinations, A and B using the above address and then if we create two consumers per each destination,

a) The consumers created using Destination B will be subscribing to the same queue as it's a named queue.
b) For the two consumers created using Destination A, should they use the same temp queue or should they each create a different temp queue ?

For (b) it should create unique temp queues for each subscriber. This needs to be taken into account when working out the caching mechanism.