2 Replies Latest reply on Apr 12, 2013 2:59 AM by Naoki Nishihara

    org.jboss.sun.net.httpserver.ServerImpl does not contains the workaround of the jdk epoll bug?

    Naoki Nishihara Newbie



      Linux Kernel:



      Java version:

      Java(TM) SE Runtime Environment (build 1.6.0_17-b04)


      JBoss version:

      JBoss EAP 6.0.0


      After I reload the JBoss web console, ServerImpl#Dispatcher thread start to use 100% cpu.


      I think this is the jdk epollWait bug, but I can't reproduce this with JDK 1.6.0_18 or higher.But the jdk's release note does not describe about this bug.



      This is the dump of the thread that uses 100% cpu.


      "Thread-37" prio=10 tid=0x00002aaae8294c00 nid=0x1e97 runnable [0x0000000043a35000..0x0000000043a35a90]

         java.lang.Thread.State: RUNNABLE

                at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)

                at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:233)

                at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:83)

                at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)

                - locked <0x00002aaabf03eee0> (a sun.nio.ch.Util$1)

                - locked <0x00002aaabf03eec8> (a java.util.Collections$UnmodifiableSet)

                - locked <0x00002aaabf451bd8> (a sun.nio.ch.EPollSelectorImpl)

                at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:106)

                at org.jboss.sun.net.httpserver.ServerImpl$Dispatcher.run(ServerImpl.java:445)

                at java.lang.Thread.run(Thread.java:636)



      This problem does not happen with the newest jdk 1.6 ?


      Best regards