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/03/27 21:58:32 UTC
[jira] Created: (RIVER-17) Misleading logging message when
discovery constraint checking is delayed
Misleading logging message when discovery constraint checking is delayed
------------------------------------------------------------------------
Key: RIVER-17
URL: https://issues.apache.org/jira/browse/RIVER-17
Project: River
Issue Type: Bug
Components: Contributions
Environment: All river platforms
Reporter: Thomas Vinod Johnson
Assigned To: Thomas Vinod Johnson
Priority: Trivial
The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
First reported here:
http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (RIVER-17) Misleading logging message when discovery
constraint checking is delayed
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer closed RIVER-17.
-----------------------------
Resolution: Fixed
Fixed and reviewed by Vinod.
> Misleading logging message when discovery constraint checking is delayed
> ------------------------------------------------------------------------
>
> Key: RIVER-17
> URL: https://issues.apache.org/jira/browse/RIVER-17
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_discovery
> Affects Versions: jtsk_2.1
> Environment: All river platforms
> Reporter: Thomas Vinod Johnson
> Assignee: Mark Brouwer
> Priority: Trivial
> Fix For: AR2
>
>
> The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
> First reported here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-17) Misleading logging message when
discovery constraint checking is delayed
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-17:
------------------------------
Fix Version/s: AR2
> Misleading logging message when discovery constraint checking is delayed
> ------------------------------------------------------------------------
>
> Key: RIVER-17
> URL: https://issues.apache.org/jira/browse/RIVER-17
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_discovery
> Affects Versions: jtsk_2.1
> Environment: All river platforms
> Reporter: Thomas Vinod Johnson
> Assignee: Mark Brouwer
> Priority: Trivial
> Fix For: AR2
>
>
> The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
> First reported here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (RIVER-17) Misleading logging message when
discovery constraint checking is delayed
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer reassigned RIVER-17:
---------------------------------
Assignee: Mark Brouwer (was: Thomas Vinod Johnson)
> Misleading logging message when discovery constraint checking is delayed
> ------------------------------------------------------------------------
>
> Key: RIVER-17
> URL: https://issues.apache.org/jira/browse/RIVER-17
> Project: River
> Issue Type: Bug
> Components: Contributions
> Environment: All river platforms
> Reporter: Thomas Vinod Johnson
> Assigned To: Mark Brouwer
> Priority: Trivial
>
> The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
> First reported here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (RIVER-17) Misleading logging message when
discovery constraint checking is delayed
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on RIVER-17 started by Mark Brouwer.
> Misleading logging message when discovery constraint checking is delayed
> ------------------------------------------------------------------------
>
> Key: RIVER-17
> URL: https://issues.apache.org/jira/browse/RIVER-17
> Project: River
> Issue Type: Bug
> Components: Contributions
> Environment: All river platforms
> Reporter: Thomas Vinod Johnson
> Assigned To: Mark Brouwer
> Priority: Trivial
>
> The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
> First reported here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (RIVER-17) Misleading logging message when
discovery constraint checking is delayed
Posted by "Mark Brouwer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-17:
------------------------------
Component/s: (was: Contributions)
com_sun_jini_discovery
Affects Version/s: jtsk_2.1
> Misleading logging message when discovery constraint checking is delayed
> ------------------------------------------------------------------------
>
> Key: RIVER-17
> URL: https://issues.apache.org/jira/browse/RIVER-17
> Project: River
> Issue Type: Bug
> Components: com_sun_jini_discovery
> Affects Versions: jtsk_2.1
> Environment: All river platforms
> Reporter: Thomas Vinod Johnson
> Assignee: Mark Brouwer
> Priority: Trivial
>
> The DiscoveryV2 utility allows the client to delay checking of constraints on multicast announcement and requests. However, even when constraint checking is delayed, the logging messages in the decodeMulticastAnnouncement and decodeMulticastRequest methods imply that constraint checking has been done. This can be misleading.
> First reported here:
> http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200703.mbox/%3c4608EA06.7070002@cheiron.org%3e
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.