[jboss-jira] [JBoss JIRA] Closed: (JBNAME-47) NamingContext.discoverServer shouldn't join multicast group
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Sat Feb 13 10:51:10 EST 2010
[ https://jira.jboss.org/jira/browse/JBNAME-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry closed JBNAME-47.
----------------------------------
Fix Version/s: 5.0.5.GA
Resolution: Done
> NamingContext.discoverServer shouldn't join multicast group
> -----------------------------------------------------------
>
> Key: JBNAME-47
> URL: https://jira.jboss.org/jira/browse/JBNAME-47
> Project: JBoss Naming
> Issue Type: Bug
> Components: jnpserver
> Affects Versions: 5.0.4.GA
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 5.1.0.Beta1, 5.0.5.GA
>
>
> NamingContext.discoverServer invokes the joinGroup method on the MulticastSocket is creates. It uses the socket to 1) send a multicast message and 2) received a UDP unicast reply. There is no need to join the group to send to it. Joining just raises the (slight) possibility of incorrectly receiving someone else's multicast discovery message instead of the desired unicast reply.
--
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
More information about the jboss-jira
mailing list