You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Brian Murphy (JIRA)" <ji...@apache.org> on 2007/08/04 19:50:53 UTC
[jira] Created: (RIVER-198) JoinManager spec should recommend a
termination order of JM first, then LDM
JoinManager spec should recommend a termination order of JM first, then LDM
---------------------------------------------------------------------------
Key: RIVER-198
URL: https://issues.apache.org/jira/browse/RIVER-198
Project: River
Issue Type: Bug
Components: net_jini_lookup
Affects Versions: jtsk_1.2
Reporter: Brian Murphy
Priority: Minor
Bugtraq ID [4520551|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4520551]
Related Bugs
Submit Date 29-OCT-2001
Description
Although the JoinManager specification leaves much of its termination
semantics undefined, that section of the spec should be changed to state
that when an application supplies a LookupDiscoveryManager to the JoinManager
and the application wants to terminate both utilities, the recommended
order of termination is:
- terminate the JoinManager first, then
- terminate the LookupDiscoveryManager
Work Around
N/A
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.