[jira] Created: (RIVER-158) SelectionManager should use Selector.wakeup() instead of custom wakeup mechanism

["Bob Scheifler (JIRA)" <ji...@apache.org>]

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

                 Key: RIVER-158
                 URL: https://issues.apache.org/jira/browse/RIVER-158
             Project: River
          Issue Type: Improvement
          Components: net_jini_jeri
    Affects Versions: jtsk_2.0
            Reporter: Bob Scheifler
            Priority: Trivial


Bugtraq ID [4857137|http://bugs.sun.com/bugdatabase/view_bug.do?bug_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.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.