-
Bug
-
Resolution: Fixed
-
P4
-
6
-
b26
-
windows
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8188758 | 9 | Ivan Gerasimov | P4 | Closed | Won't Fix | |
JDK-8196267 | 8u191 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8201118 | 8u181 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8188759 | 8u172 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8203116 | emb-8u181 | Ivan Gerasimov | P4 | Resolved | Fixed | master |
JDK-8188760 | 7u181 | Ivan Gerasimov | P4 | Resolved | Fixed | b01 |
JDK-8188761 | 6u191 | Ivan Gerasimov | P4 | Resolved | Fixed | b02 |
It also suggests (in the example code) to do a few retries in a case of a failure due to insufficient buffer size).
We have reports that the number of the network adaptors can change at the early stage of the OS boot cycle, so if a Java application is running at that time it can experience a trouble because of too small buffer.
It seems to be a correct approach to follow the recommendations from MSDN in this case.
[1] https://msdn.microsoft.com/en-us/library/windows/desktop/aa365915(v=vs.85).aspx
- backported by
-
JDK-8188759 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8188760 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8188761 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8196267 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8201118 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8203116 Bigger buffer for GetAdaptersAddresses
-
- Resolved
-
-
JDK-8188758 Bigger buffer for GetAdaptersAddresses
-
- Closed
-
- relates to
-
JDK-8188855 Fix VS10 build after "8187658: Bigger buffer for GetAdaptersAddresses"
-
- Closed
-
- links to