[teiid-issues] [JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu
Kylin Soong (JIRA)
issues at jboss.org
Wed Sep 3 04:08:59 EDT 2014
[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998227#comment-12998227 ]
Kylin Soong commented on TEIID-3070:
------------------------------------
This is a well known JDK bug in netty, it be well discussed in [1].
Netty 3.5.6.Final released notes [2] have refer this, a workaround [3] be added in this release, but it be removed later from the commit history [4].
[1] https://github.com/netty/netty/issues/327
[2] http://netty.io/news/2012/08/30/3-5-6-final.html
[3] https://github.com/netty/netty/commit/ff3f2b6361a48dc61956999945df0d2e9e2d4886
[4] https://github.com/netty/netty/commits/3.6/src/main/java/org/jboss/netty/channel/socket/nio/AbstractNioWorker.java
> Netty worker threads cause system high cpu
> ------------------------------------------
>
> Key: TEIID-3070
> URL: https://issues.jboss.org/browse/TEIID-3070
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Server
> Affects Versions: 8.7
> Environment: JDV 6.1.0.DR2
> JDV 6.0
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> I have hit this issue many times in deploying a VDB to JDV, All CPU be used by netty worker threads:
> ~~~
> "New I/O worker #3" daemon prio=10 tid=0x00007fc71c0d2000 nid=0x320b runnable [0x00007fc7074f3000]
> java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
> - locked <0x00000000c42b4318> (a sun.nio.ch.Util$2)
> - locked <0x00000000c42b4328> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000c42b42d0> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
> at org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:64)
> ~~~
> Seems this is a exist netty issue, search "jboss netty high cpu" via google we can get lots of result.
> Below link have detailed depiction about this issue;
> https://github.com/kylinsoong/teiid-samples/tree/master/highcpu
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the teiid-issues
mailing list