You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Simon Temple (JIRA)" <ji...@apache.org> on 2006/04/10 10:37:58 UTC
[jira] Created: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
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
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
[jira] Commented: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-204?page=comments#action_12376397 ]
Trustin Lee commented on DIRMINA-204:
-------------------------------------
Please close this issue, Simon.
> 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
[jira] Commented: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Simon Temple (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-204?page=comments#action_12373838 ]
Simon Temple commented on DIRMINA-204:
--------------------------------------
Not a bug, please close this call.
> 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
>
> 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
[jira] Closed: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Simon Temple (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-204?page=all ]
Simon Temple closed DIRMINA-204:
--------------------------------
Closed as requested
> 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
[jira] Commented: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Simon Temple (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-204?page=comments#action_12373836 ]
Simon Temple commented on DIRMINA-204:
--------------------------------------
Apologies... this appears to be a problem when running Java 1.4.1
When running 1.4.2_07 we see very low CPU utilisation when the network is disabled and re-enabled.
I'd guess that the JDK 1.4.1 implementation of poll() spins out of control and 1.4.2 does not:
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:262)
at sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:244)
at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:127)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:62)
If anyone can educate me about this I'd be pleased to hear from them.
TIA
> 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
>
> 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
[jira] Commented: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Norbert Reilly (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (DIRMINA-204) Network disconnection (or initial
connection) once SocketAcceptor is running causes 100% CPU consumption on
Windows
Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRMINA-204?page=all ]
Trustin Lee resolved DIRMINA-204:
---------------------------------
Resolution: Invalid
Assign To: Trustin Lee
It is not our bug but JDK 1.4.1's bug. Thank you for investigating on this issue for us, Simon!
> 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