Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8071599

(so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P3
    • 9
    • 9
    • core-libs
    • b54
    • Verified

    Backports

      Description

        sc.socket().sendUrgentData(b) throws IllegalBlockingMode when channel configured non-blocking. This is correct behavior because java.net.Socket is blocking only and Socket operations are expected to block.

        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.




        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8074143 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8076888 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8083971 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8086812 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8138212 (so) Socket adapter sendUrgentData throws IllegalBlockingMode when channel configured non-blocking

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                bpb Brian Burkhalter
                alanb Alan Bateman
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: