[RIVER-17] Misleading logging message when discovery constraint checking is delayed

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: com_sun_jini_discovery

Environment

All river platforms

• Assignee: Mark Brouwer
• Reporter: Thomas Vinod Johnson
• Created: 27/Mar/07 19:58
• Updated: 02/Feb/08 11:04
• Resolved: 02/Feb/08 11:04

Description

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/[e-mail]%3e