[ http://issues.apache.org/jira/browse/DIRMINA-204?page=comments#action_12376392 ]
Norbert Reilly commented on DIRMINA-204: ---------------------------------------- Confirmed against ApacheDS 1.0 RC1 (refer http://issues.apache.org/jira/browse/DIRSERVER-608 ) that the problem went away when upgraded to JDK 1.4.2_11 > Network disconnection (or initial connection) once SocketAcceptor is running > causes 100% CPU consumption on Windows > ------------------------------------------------------------------------------------------------------------------- > > Key: DIRMINA-204 > URL: http://issues.apache.org/jira/browse/DIRMINA-204 > Project: Directory MINA > Type: Bug > Versions: 0.9.3 > Environment: JDK 1.4.2_07, Windows 2000 > Reporter: Simon Temple > Assignee: Trustin Lee > > SocketAcceptorDelegate Thread appears to be skipping the Thread.Sleep() > because the interrupted attribute of the Thread is set because the selector > operation dropped through... I think ;-) > "SocketAcceptor-0" prio=5 tid=0x1784FCD0 nid=0x92c runnable > [1802f000..1802fd88] > at java.lang.Thread.isInterrupted(Native Method) > at java.lang.Thread.isInterrupted(Thread.java:771) > at java.nio.channels.spi.AbstractSelector.begin(AbstractSelector.java:198) > at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:125) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:62) > - locked <040E09F0> (a sun.nio.ch.SelectorImpl$Lock) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:67) > at > org.apache.mina.transport.socket.nio.support.SocketAcceptorDelegate$Worker.run(SocketAcceptorDelegate.java:326) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
