You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jim Waldo (JIRA)" <ji...@apache.org> on 2007/07/26 17:03:04 UTC
[jira] Created: (RIVER-58) LookupDiscovery with no groups
unnecessarily consumes a thread
LookupDiscovery with no groups unnecessarily consumes a thread
--------------------------------------------------------------
Key: RIVER-58
URL: https://issues.apache.org/jira/browse/RIVER-58
Project: River
Issue Type: Improvement
Components: com_sun_jini_discovery
Affects Versions: jtsk_2.1
Reporter: Jim Waldo
Priority: Minor
A LookupDiscovery instance configured with no groups still receives
multicast announcements. In the non-secure case this doesn't impose a
large computational cost, but when receiving signed announcements,
especially a few per minute, there is a significant computational cost
in verifying signatures, only to toss the announcements anyway. The
AnnouncementListener thread shouldn't be run when there are no groups.
A particular example where this can easily come up is in reggie itself,
which by default as a LookupDiscovery with no groups.
LookupDiscovery currently discards announcements which are not of interest before verifying the signature. This behavior further reduces the need for this bug fix. While there is still the issue of an extra unwanted thread lying around in this case, the major issue of a heavy compute load due to signature verification completely goes away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-58) LookupDiscovery with no groups
unnecessarily consumes a thread
Posted by "Bob Scheifler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Scheifler updated RIVER-58:
-------------------------------
Component/s: (was: com_sun_jini_discovery)
net_jini_discovery
> LookupDiscovery with no groups unnecessarily consumes a thread
> --------------------------------------------------------------
>
> Key: RIVER-58
> URL: https://issues.apache.org/jira/browse/RIVER-58
> Project: River
> Issue Type: Improvement
> Components: net_jini_discovery
> Affects Versions: jtsk_2.1
> Reporter: Jim Waldo
> Priority: Minor
>
> A LookupDiscovery instance configured with no groups still receives
> multicast announcements. In the non-secure case this doesn't impose a
> large computational cost, but when receiving signed announcements,
> especially a few per minute, there is a significant computational cost
> in verifying signatures, only to toss the announcements anyway. The
> AnnouncementListener thread shouldn't be run when there are no groups.
> A particular example where this can easily come up is in reggie itself,
> which by default as a LookupDiscovery with no groups.
> LookupDiscovery currently discards announcements which are not of interest before verifying the signature. This behavior further reduces the need for this bug fix. While there is still the issue of an extra unwanted thread lying around in this case, the major issue of a heavy compute load due to signature verification completely goes away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.