You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Simon IJskes (JIRA)" <ji...@apache.org> on 2012/10/05 10:24:47 UTC
[jira] [Updated] (RIVER-174) LookupDiscovery could use a
WakeupManager to schedule its announcement timeout check.
[ https://issues.apache.org/jira/browse/RIVER-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon IJskes updated RIVER-174:
-------------------------------
Assignee: (was: Mark Brouwer)
> LookupDiscovery could use a WakeupManager to schedule its announcement timeout check.
> -------------------------------------------------------------------------------------
>
> Key: RIVER-174
> URL: https://issues.apache.org/jira/browse/RIVER-174
> Project: River
> Issue Type: Improvement
> Components: net_jini_discovery
> Affects Versions: jtsk_2.1
> Reporter: Phil Steitz
> Priority: Minor
> Fix For: River_2.2.1
>
>
> Bugtraq ID [6265299|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6265299]
> LookupDiscovery currently has a separate thread that checks for announcement timeouts. It could use its WakeupManager to schedule this task instead.
> xxxxx@xxxxx 2005-05-04 15:21:21 GMT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira