[
https://jira.jboss.org/jira/browse/JGRP-857?page=com.atlassian.jira.plugi...
]
Bela Ban resolved JGRP-857.
---------------------------
Resolution: Done
Solved by checking in PING and MPING whether own discovery requests are received - if not,
log a WARN
UDP transport to attempt to validate ability to receive own
multicast
---------------------------------------------------------------------
Key: JGRP-857
URL:
https://jira.jboss.org/jira/browse/JGRP-857
Project: JGroups
Issue Type: Feature Request
Reporter: Brian Stansberry
Assignee: Bela Ban
Priority: Minor
Fix For: 2.6.7, 2.7
One category of errors JGroups users see is improperly configured multicast on the
interface the transport is using.
Could the UDP transport help here? Perhaps send a multicast message during the channel
connect phase, and block a short period on a future waiting to receive your own message.
If the message isn't received, log an ERROR with a nice helpful diagnostic.
Probably set a timeout for how long to wait with a default that disables this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira