You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Thomas Vinod Johnson (JIRA)" <ji...@apache.org> on 2007/07/27 16:51:18 UTC
[jira] Updated: (RIVER-106) JoinManager could use a notion of
failed lookup service without discard
[ https://issues.apache.org/jira/browse/RIVER-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Vinod Johnson updated RIVER-106:
---------------------------------------
Description:
Bugtraq ID [6365106|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6365106]
JoinManager currently calls discard on the underlying DiscoveryManagement utility if it encounters exceptions when trying to use ServiceRegistrar proxies that the utility discovers for it. In certain cases such as when it encounters an UnsupportedConstraintException in proxy preparation, it may makes more sense to simply ignore the proxy in the future rather than actively discard it. In this case, forcing discard and consequent rediscovery of the proxy does not seem warranted, since JoinManager will not be able to use it after it has been rediscovered anyway.
Evaluation: Simply ignoring the discarded proxy, as is suggested in the description, may not be a viable solution. This is because the discovery manager used by the JoinManager may be shared by other entities that do not wish to ignore the proxy.
Needs further thought on how the JoinManager should go about ignoring the proxy, as well as the ramifications of doing so.
Also see: Bugtraq ID [6364552|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6364552]
was:
Bugtraq ID [6365106|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6365106]
JoinManager currently calls discard on the underlying DiscoveryManagement utility if it encounters exceptions when trying to use ServiceRegistrar proxies that the utility discovers for it. In certain cases such as when it encounters an UnsupportedConstraintException in proxy preparation, it may makes more sense to simply ignore the proxy in the future rather than actively discard it. In this case, forcing discard and consequent rediscovery of the proxy does not seem warranted, since JoinManager will not be able to use it after it has been rediscovered anyway.
Evaluation: Simply ignoring the discarded proxy, as is suggested in the description, may not be a viable solution. This is because the discovery manager used by the JoinManager may be shared by other entities that do not wish to ignore the proxy.
Needs further thought on how the JoinManager should go about ignoring the proxy, as well as the ramifications of doing so.
Also see: Bugtraq ID [6364552http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6364552]
Fix also see bugraq id URL
> JoinManager could use a notion of failed lookup service without discard
> -----------------------------------------------------------------------
>
> Key: RIVER-106
> URL: https://issues.apache.org/jira/browse/RIVER-106
> Project: River
> Issue Type: Improvement
> Components: net_jini_discovery
> Affects Versions: jtsk_2.1
> Reporter: Thomas Vinod Johnson
>
> Bugtraq ID [6365106|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6365106]
> JoinManager currently calls discard on the underlying DiscoveryManagement utility if it encounters exceptions when trying to use ServiceRegistrar proxies that the utility discovers for it. In certain cases such as when it encounters an UnsupportedConstraintException in proxy preparation, it may makes more sense to simply ignore the proxy in the future rather than actively discard it. In this case, forcing discard and consequent rediscovery of the proxy does not seem warranted, since JoinManager will not be able to use it after it has been rediscovered anyway.
> Evaluation: Simply ignoring the discarded proxy, as is suggested in the description, may not be a viable solution. This is because the discovery manager used by the JoinManager may be shared by other entities that do not wish to ignore the proxy.
> Needs further thought on how the JoinManager should go about ignoring the proxy, as well as the ramifications of doing so.
> Also see: Bugtraq ID [6364552|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6364552]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.