[jboss-jira] [JBoss JIRA] (JGRP-1878) Multicast discovery does not work on JDK8

Bela Ban (JIRA) issues at jboss.org
Fri Sep 5 03:07:01 EDT 2014


    [ https://issues.jboss.org/browse/JGRP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999194#comment-12999194 ] 

Bela Ban commented on JGRP-1878:
--------------------------------

So if we had {{IP_MULTICAST_ALL}} set to 1, we'd get the old behavior ?

Do you know when socket option {{IP_MULTICAST_ALL}} will be supported ? JDK 8 ? (I checked; it is not in JDK 7).

In [1] I'll need to set socket option {{IP_MULTICAST_TTL}}, so I might as well also set the {{IP_MULTICAST_ALL}} option, when supported.

The question is, should 1 be the default ? I actually think that we should only receive traffic on interfaces on which we joined a multicast group, so 0 is just fine IMO.

[1] https://issues.jboss.org/browse/JGRP-1880

> Multicast discovery does not work on JDK8
> -----------------------------------------
>
>                 Key: JGRP-1878
>                 URL: https://issues.jboss.org/browse/JGRP-1878
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.2.12, 3.5
>         Environment: OpenJDK8, OracleJDK8u40
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Minor
>             Fix For: 3.2.14, 3.6
>
>         Attachments: mcast.java
>
>
> Multicast discovery does not work on JDK8 when using different bind IP addresses. This blocks EAP certification on JDK8.
> Steps to reproduce with draw, switch to JDK8:
> {noformat}
> export IP_ADDR=127.0.0.1
> ./draw.sh
> export IP_ADDR=192.168.1.10
> ./draw.sh
> {noformat}
> Everything works when binding to the same IP address or using JDK 6 or 7. Possibly a JDK8 bug..



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jboss-jira mailing list