Uploaded image for project: 'River (Retired)'
  1. River (Retired)
  2. RIVER-158

SelectionManager should use Selector.wakeup() instead of custom wakeup mechanism

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Trivial
    • Resolution: Unresolved
    • jtsk_2.0
    • None
    • net_jini_jeri
    • None
    • 4857137

    Description

      Bugtraq ID 4857137

      When com.sun.jini.jeri.internal.runtime.SelectionManager was originally written, the java.nio.channels.Selecor.wakeup() method was buggy and behaved differently on different OSes. SelectionManager needed Selector.wakeup()-like behavior, but to work around to the bugs, it instead uses a custom wakeup mechanism of a java.nio.channels.Pipe registered with the selector, sending bytes to the pipe in order to wake it up. If it can now be determined that Selector.wakeup() works reliably on all platforms and J2SE versions of interest, then this workaround should be removed and replace with invocations of Selector.wakeup(), in order to clean up the code and (perhaps negligibly) improve performance.

      Attachments

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. RIVER-318 JERI Performance Issues

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            People

              Unassigned Unassigned
              rscheifler Robert Scheifler
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: