You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2015/07/07 16:46:05 UTC

[jira] [Commented] (AMQ-5848) The noLocal state for a durable subscription is not stored and recovered.

    [ https://issues.apache.org/jira/browse/AMQ-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616797#comment-14616797 ] 

Timothy Bish commented on AMQ-5848:
-----------------------------------

The final bit of this is to up the openwire version that we use in the KahaDB store to v11, current default is v6.  This would cause any existing stores that people tried to reuse when updating the broker (not recommended but people do it).  We currently do track the version used in the store in the index metadata so the solution would be to ignore the default or any set value and use the one from the existing store and log a warning that some newer broker features may not work while operating with a legacy store.

> The noLocal state for a durable subscription is not stored and recovered.
> -------------------------------------------------------------------------
>
>                 Key: AMQ-5848
>                 URL: https://issues.apache.org/jira/browse/AMQ-5848
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP, Broker, JMS client, KahaDB
>    Affects Versions: 5.10.0, 5.10.1, 5.10.2, 5.11.0, 5.11.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.12.0
>
>
> The broker does not store the noLocal value as part of the SubscriptionInfo object that represents stored durable subscriptions.  This means that on restart the value for previous subscriptions is not recovered from the store which means we can fail tests for this bit in the JMS spec:
> {quote}
> If an unshared durable subscription already exists with the same name and client identifier but a different topic, message selector or noLocal value has been specified, and there is no consumer already active (i.e. not closed) on the durable subscription then this is equivalent to unsubscribing (deleting) the old one and creating a new one. 
> {quote}
> This also means that an AMQP receiver that tries to recover a previous durable subscription won't be able to validate the remote Source to validate that its state matches the requested subscription configuration. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)