[jira] Updated: (RIVER-11) LookupLocatorDiscovery ignores new LookupLocator instances for which only constraints differ

["Mark Brouwer (JIRA)" <ji...@apache.org>]

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

Mark Brouwer updated RIVER-11:
------------------------------

          Component/s: net_jini_discovery
    Affects Version/s: jtsk_2.1

> LookupLocatorDiscovery ignores new LookupLocator instances for which only constraints differ
> --------------------------------------------------------------------------------------------
>
>                 Key: RIVER-11
>                 URL: https://issues.apache.org/jira/browse/RIVER-11
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.1
>            Reporter: Mark Brouwer
>
> When you modify the set of {{LookupLocator}} in use by {{LookupLocatorDiscovery}} the lookup locators considered equal as in {{LookupLocator.equals}} are ignored, although they can carry different constraints with them such as with {{ConstrainableLookupLocator}}. This means that when unicast discovery fails for a lookup locator due to 'wrong' constraints, and you pass in a new lookup locator with different constraints (that might make discovery possible) the retries will continue with the earlier lookup locator passed in.
> The problem here is that lookup locator equality is or not properly specified, or the {{LookupLocatorDiscovery}} utility must assume lookup locators passed have non-trivial characteristics that won't surface by calling equals on them.
> This issue is closely related to how we should deal with changing security requirements over time.

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