river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Created] (RIVER-466) ServiceDiscoveryManager not exiting lookup loop when serviceItems.length >= minMatches
Date Sun, 13 May 2018 19:57:00 GMT
Shawn Ellis created RIVER-466:
---------------------------------

             Summary: ServiceDiscoveryManager not exiting lookup loop when serviceItems.length
>= minMatches
                 Key: RIVER-466
                 URL: https://issues.apache.org/jira/browse/RIVER-466
             Project: River
          Issue Type: Bug
          Components: net_jini_lookup
    Affects Versions: River_3.0.0
            Reporter: Shawn Ellis
         Attachments: MinMatches.patch

The problem occurs when a lookup for only one service is required, but more than one is found.
Currently, the lookup loop only exits if the number of services found is equivalent to the
minMatches or the timeout has expired.

How to Reproduce:
 1. Have multiple instances of a service registered with reggie.
 2. Have a client call that performs a lookup with a constraint of only one service
  
{code:java}
lookup(serviceTemplate, 1, 1, null, 30 * 100){code}
3. The lookup loop will not exit until the timeout has expired even though more than minMatches
were found.

The attached patch causes the lookup loop to be exited which results in less time to service
lookups.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message