Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
0.20.204.0
-
None
-
None
Description
We are seeing some TaskTracker jetty servers stuck in a tight loop. This appears to be related to Jetty bug 937 (http://jira.codehaus.org/browse/JETTY-937).
stack trace for this thread 15993(0x3e79) showing a loop in jetty.
"21006965@qtp-11400638-0 - Acceptor0 SelectChannelConnector@0.0.0.0:50060" prio=10 tid=0x08e6d400 nid=0x3e79
runnable [0xaddfb000]
java.lang.Thread.State: RUNNABLE
at java.lang.Throwable.fillInStackTrace(Native Method)
- locked <0xdf2708e8> (a java.io.IOException)
at java.lang.Throwable.<init>(Throwable.java:196)
at java.lang.Exception.<init>(Exception.java:41)
at java.io.IOException.<init>(IOException.java:41)
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:210)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69) - locked <0xb6524f58> (a sun.nio.ch.Util$1)
- locked <0xb6524f68> (a java.util.Collections$UnmodifiableSet)
- locked <0xb6400930> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:88)
at org.mortbay.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:652)
at org.mortbay.io.nio.SelectorManager.doSelect(SelectorManager.java:192)
at org.mortbay.jetty.nio.SelectChannelConnector.accept(SelectChannelConnector.java:124)
at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:708)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Attachments
Issue Links
- duplicates
-
MAPREDUCE-2386 TT jetty server stuck in tight loop around epoll_wait
- Open
- relates to
-
MAPREDUCE-2386 TT jetty server stuck in tight loop around epoll_wait
- Open