You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/09/05 16:17:44 UTC

[jira] Created: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Changing a DurableSubscriber's Selector does not remove the old binding
-----------------------------------------------------------------------

                 Key: QPID-1275
                 URL: https://issues.apache.org/jira/browse/QPID-1275
             Project: Qpid
          Issue Type: Bug
            Reporter: Martin Ritchie


This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)

BDBUpgradeTest.testDurabilitySelectors

On recovery there are two binding values for the Durable Subscriber:

main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})

Steps to reproduce.

Create DurableSubscriber with no selector
Close subscriber
Create DurableSubscriber with selector odd=true
Close subscriber
Restart broker.


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


[jira] Updated: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1275:
---------------------------------

    Affects Version/s: M4

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Client
>    Affects Versions: M3, M4
>            Reporter: Martin Ritchie
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

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


[jira] Updated: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1275:
---------------------------------

        Fix Version/s: M4
    Affects Version/s: M3

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>             Fix For: M4
>
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

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


[jira] Updated: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1275:
---------------------------------

    Component/s: Java Client

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>             Fix For: M4
>
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

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


[jira] Updated: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-1275:
-----------------------------------

    Fix Version/s:     (was: M4)

Descoping items not being worked on for M4 into Unknown Fix Version for now

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Client
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

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


[jira] Updated: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Ritchie updated QPID-1275:
---------------------------------

    Component/s: Java Broker

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Client
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>             Fix For: M4
>
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

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


[jira] Commented: (QPID-1275) Changing a DurableSubscriber's Selector does not remove the old binding

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675352#action_12675352 ] 

Martin Ritchie commented on QPID-1275:
--------------------------------------

There is code in the client to detect when a subscription changes however the test makes a new fresh connection so is unaware that there is an existing subscription.

The broker however is aware of the existing subscription and does not recognise the new durable subscription as a replacement. Hence we end up with the topic being bound twice. 

> Changing a DurableSubscriber's Selector does not remove the old binding
> -----------------------------------------------------------------------
>
>                 Key: QPID-1275
>                 URL: https://issues.apache.org/jira/browse/QPID-1275
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker, Java Client
>    Affects Versions: M3, M4
>            Reporter: Martin Ritchie
>
> This can be evidenced with the BDBMessageStore (DerbyMessageStore upgrade still pending)
> BDBUpgradeTest.testDurabilitySelectors
> On recovery there are two binding values for the Durable Subscriber:
> main 2008-09-05 15:01:43,801 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: null)
> main 2008-09-05 15:01:43,802 INFO [server.store.berkeleydb.BDBMessageStore] Restoring binding: (Exchange: amq.topic, Queue: clientid:MySubscription, Routing Key: MyDurableSubscriptionTestTopic, Arguments: {x-filter-jms-selector=[LONG_STRING: odd=true]})
> Steps to reproduce.
> Create DurableSubscriber with no selector
> Close subscriber
> Create DurableSubscriber with selector odd=true
> Close subscriber
> Restart broker.

-- 
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