QPID-2881

When a topic based destination is used in creating a consumer, the code looks to see if the address is already resolved.

If it is then it could mean two things.
  1. A consumer is being recreated after failover.
  2. This destination was used previously to create a consumer or a producer. In this case we assume it was used for a consumer.

For case #1, we need to preserve the queue name. The reason being if it was either a durable subscription or if it was a named queue (name property specified in link) then we need to maintain the same name.

For case #2 we need to ensure that each consumer gets it's own queue,hence we clone the destination object and the queue name is set to null
so name is auto-generated.

I have removed the incorrect logic (in BasicMessageConsumer_0_10) of looking at the durable property as one factor in deciding if it's case #1.
A durable subscription does use a named queue, therefore it is not nessacery to look at the durable property in order to identify it as case #1.
I have made modifications to createDurableTopic method in AMQTopic to set the queue name in the link properties.

The above changes enable a user to create more than one consumer (each with it's own unique queue) when using the same destination created off an addressing string that has durable set to true.


git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@999704 13f79535-47bb-0310-9956-ffa450edef68

0 files changed, 0 insertions, 0 deletions