[jira] [Resolved] (RIVER-395) Ill-behaved DiscoveryListener can terminate discovery notifier threads

["Peter Firmstone (JIRA)" <ji...@apache.org>]

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

Peter Firmstone resolved RIVER-395.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: River_3.0.0

> Ill-behaved DiscoveryListener can terminate discovery notifier threads
> ----------------------------------------------------------------------
>
>                 Key: RIVER-395
>                 URL: https://issues.apache.org/jira/browse/RIVER-395
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.1
>            Reporter: Chris Dolan
>             Fix For: River_3.0.0
>
>         Attachments: discovery_listener_safety.patch
>
>
> (bug detected in Jini 2.1, still present in 2.1.2+ trunk)
> If a net.jini.discovery.DiscoveryListener implementation throws an unchecked exception, then the LookupLocatorDiscovery$Notifier thread and/or the LookupDiscovery$Notifier thread will exit prematurely. In practice, this can prevent the JoinManager$DiscMgrListener or ServiceDiscoveryManager$DiscMgrListener callbacks from being invoked, resulting in incomplete state for a registrar.
> A soon-to-be attached patch surrounds each listener invocation with a try/catch block.



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