JDK-8179559 : Solaris MulticastSocket issues
- Type: Bug
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 10
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-05-03
- Updated: 2021-05-13
- Resolved: 2017-05-08
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 10 | JDK 8 |
|---|---|
10 b07Fixed  |
8u311Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Two Solaris issues with Multicast sockets which seem to arise when IPv6 is enabled but a number of interfaces do not have a normal IPv6 address assigned. Instead the system reports that each interface has the address ::0 assigned. 1. First issue is that MulticastSocket.getInterface() uses NetworkInterface.getByInetAddress() to retrieve the interface from the socket's multicast interface address. If that address is ::0 then this logic is broken because there can be multiple interfaces with ::0 assigned. Solution is to cycle through all interfaces looking for the socket's multicast interface address. 2. IPv6 multicasting does not work on Solaris unless the network interface used has a normal IPv6 address assigned (other than ::0). A number of tests need to be changed to check for ::0 before choosing to use IPv6 for the test.