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

Andrew Kennedy updated QPID-2418:
---------------------------------

    Attachment: 0001-QPID-2418-trunk.patch
                0001-QPID-2418-branch.patch

Revised patches. These do *not* fix this issue completely, since the 
information stored regarding subscriptions on the client is per-session, and 
should really be per-connection for behaviour to be consistent. In order not to 
introduce such inconsistent behaviour, I have changed the code to throw a JMS 
IllegalStateException on any attempt to re-create a subscription (with the same 
paramaters) that already exists on the session, and unsubscribe if the 
re-created subscription is a change to an existing open subscription on the 
session, otherwise behaviour is unchanged. The code adds locking of the 
subscription information and gets rid of duplicated code across protocol  
versions, but a complete fix for this issue will require more extensive changes.

>  Existing durable subscription with selector is not unsubscribed during 
> change to new subscription
> --------------------------------------------------------------------------------------------------
>
>                 Key: QPID-2418
>                 URL: https://issues.apache.org/jira/browse/QPID-2418
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M4, 0.5, 0.6
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>             Fix For: 0.7
>
>         Attachments: 0001-QPID-2418-branch.patch, 0001-QPID-2418-trunk.patch
>
>
> AMQSession.createDurableSubscriber(topic, name, messageSelector, noLocal) 
> does not unsubscribe existing durable subscriptions. Whilst it does check for 
> existing durable subscriptions in use by the client with the same name, it 
> instead simply closes the subscriptions then creates a new one. As a result 
> of not unsubscribing, the queue backing the subscription is not deleted 
> before being used by the updated subscription as it should be (and as happens 
> in the 0_8 and 0_10 subclasses when using durable subscriptions without 
> selectors).

-- 
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-subscr...@qpid.apache.org

Reply via email to