You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@river.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/05/05 05:14:03 UTC

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

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

Hudson commented on RIVER-395:
------------------------------

Integrated in River-trunk #481 (See [https://builds.apache.org/hudson/job/River-trunk/481/])
    RIVER-395
Bad listener tests, first version.


> 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
>         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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira