-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b54
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8083971 | emb-9 | Brian Burkhalter | P3 | Resolved | Fixed | team |
JDK-8086812 | 8u65 | Brian Burkhalter | P3 | Resolved | Fixed | b01 |
JDK-8074143 | 8u60 | Brian Burkhalter | P3 | Resolved | Fixed | b06 |
JDK-8138212 | emb-8u65 | Unassigned | P3 | Resolved | Fixed | b01 |
JDK-8076888 | emb-8u60 | Brian Burkhalter | P3 | Resolved | Fixed | team |
It has been suggested that that sendUrgentData should work with SocketChannel's configured non-blocking. In order to do this then it requires understanding how send(MSG_OOB) behaves when the socket buffer is full and whether send can return EAGAIN/EWOULDBLOCK.
The data that have so far is:
Linux - returns EAGAIN/EWOULDBLOCK
OSX - fails with "No buffer space available"
Windows - fails with " Resource temporarily unavailable: no further information"
The I/O error is okay as that is allowed by the spec.
- backported by
-
JDK-8074143 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking
-
- Resolved
-
-
JDK-8076888 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking
-
- Resolved
-
-
JDK-8083971 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking
-
- Resolved
-
-
JDK-8086812 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking
-
- Resolved
-
-
JDK-8138212 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking
-
- Resolved
-