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

["Rajith Attapattu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/QPID-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajith Attapattu resolved QPID-2809.
------------------------------------

    Resolution: Fixed

Fixed along with a test case to ensure that this does not have any unwanted side effects.
Also the failover test cases indirectly tests whether this functionality works as expected.

> Once an AMQDestination object resolves an address, it should not try to resolve it again when used in subsequent operations.  
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2809
>                 URL: https://issues.apache.org/jira/browse/QPID-2809
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Client
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.7
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org