river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Brouwer (JIRA)" <j...@apache.org>
Subject [jira] Closed: (RIVER-17) Misleading logging message when discovery constraint checking is delayed
Date Sat, 02 Feb 2008 11:06:08 GMT

     [ 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.


Mime
View raw message