Uploaded image for project: 'XNIO'
  1. XNIO
  2. XNIO-356

Channels.readBlocking with timeout overload may return spuriously

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.7.8.Final, 3.8.0.Final
    • None
    • api
    • None

    Description

      While this may have been the intended behavior, the javadoc states "This method blocks until the channel is readable, and then the message is read." which disagrees with the implementation.
      By contrast both writeBlocking and sendBlocking overloads with timeouts measure time since the request began, so it seems reasonable to standardize on that behavior.

      Attachments

        Issue Links

          Activity

            People

              flaviarnn Flavia Rainone
              carterkozak Carter Kozak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: