Michael Schlueter created DIRMINA-1011:
------------------------------------------
Summary: 100% load in Mina when using openfire 3.10.0
Key: DIRMINA-1011
URL: https://issues.apache.org/jira/browse/DIRMINA-1011
Project: MINA
Issue Type: Bug
Components: Core
Affects Versions: 2.0.9
Environment: Debian Linux 7.8 with java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-1~deb7u1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) but also Windows
installations seems to be affected
Reporter: Michael Schlueter
Priority: Critical
There are a lot of reports at openfire
(http://www.igniterealtime.org/projects/openfire/) that with version 3.10.0
which was released shortly some mina threads using 100% processor load after a
short time after starting openfire. For me the java heap shows after a day:
Thread 27833: (state = IN_NATIVE)
- sun.nio.ch.EPollArrayWrapper.epollWait(long, int, long, int) @bci=0
(Compiled frame; information may be imprecise)
- sun.nio.ch.EPollArrayWrapper.poll(long) @bci=18, line=269 (Compiled frame)
- sun.nio.ch.EPollSelectorImpl.doSelect(long) @bci=28, line=79 (Compiled frame)
- sun.nio.ch.SelectorImpl.lockAndDoSelect(long) @bci=37, line=87 (Compiled
frame)
- sun.nio.ch.SelectorImpl.select(long) @bci=30, line=98 (Compiled frame)
- org.apache.mina.transport.socket.nio.NioProcessor.select(long) @bci=5,
line=97 (Compiled frame)
- org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run()
@bci=51, line=1074 (Compiled frame)
- org.apache.mina.util.NamePreservingRunnable.run() @bci=29, line=64
(Interpreted frame)
-
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
@bci=95, line=1145 (Compiled frame)
- java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=615
(Interpreted frame)
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)
and for a second thread:
Thread 8288: (state = IN_NATIVE)
- sun.nio.ch.FileDispatcherImpl.read0(java.io.FileDescriptor, long, int)
@bci=0 (Compiled frame; information may be imprecise)
- sun.nio.ch.SocketDispatcher.read(java.io.FileDescriptor, long, int) @bci=4,
line=39 (Compiled frame)
- sun.nio.ch.IOUtil.readIntoNativeBuffer(java.io.FileDescriptor,
java.nio.ByteBuffer, long, sun.nio.ch.NativeDispatcher) @bci=114, line=223
(Compiled frame)
- sun.nio.ch.IOUtil.read(java.io.FileDescriptor, java.nio.ByteBuffer, long,
sun.nio.ch.NativeDispatcher) @bci=48, line=197 (Compiled frame)
- sun.nio.ch.SocketChannelImpl.read(java.nio.ByteBuffer) @bci=234, line=379
(Compiled frame)
-
org.apache.mina.transport.socket.nio.NioProcessor.read(org.apache.mina.transport.socket.nio.NioSession,
org.apache.mina.core.buffer.IoBuffer) @bci=10, line=311 (Compiled frame)
-
org.apache.mina.transport.socket.nio.NioProcessor.read(org.apache.mina.core.session.AbstractIoSession,
org.apache.mina.core.buffer.IoBuffer) @bci=6, line=1 (Compiled frame)
-
org.apache.mina.core.polling.AbstractPollingIoProcessor.read(org.apache.mina.core.session.AbstractIoSession)
@bci=62, line=694 (Compiled frame)
-
org.apache.mina.core.polling.AbstractPollingIoProcessor.process(org.apache.mina.core.session.AbstractIoSession)
@bci=17, line=668 (Compiled frame)
- org.apache.mina.core.polling.AbstractPollingIoProcessor.process() @bci=20,
line=657 (Compiled frame)
-
org.apache.mina.core.polling.AbstractPollingIoProcessor.access$10(org.apache.mina.core.polling.AbstractPollingIoProcessor)
@bci=1, line=654 (Compiled frame)
- org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run()
@bci=204, line=1121 (Compiled frame)
- org.apache.mina.util.NamePreservingRunnable.run() @bci=29, line=64
(Interpreted frame)
-
java.util.concurrent.ThreadPoolExecutor.runWorker(java.util.concurrent.ThreadPoolExecutor$Worker)
@bci=95, line=1145 (Compiled frame)
- java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=5, line=615
(Interpreted frame)
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)
You can find some more information in the openfire forum (see External issue
URL). In the forum you can find also some more threads with these issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
