dan jatnieks created HTTPCORE-332:
-------------------------------------
Summary: CPU spin in epollWait
Key: HTTPCORE-332
URL: https://issues.apache.org/jira/browse/HTTPCORE-332
Project: HttpComponents HttpCore
Issue Type: Bug
Affects Versions: 4.2.3
Reporter: dan jatnieks
After applying the fix suggested in HTTPCORE-331, we encountered another
instance of a thread with CPU spin. The stack trace is:
{noformat}
"Agent-005" prio=10 tid=0x00007f555c034800 nid=0xa54 runnable
[0x00007f554848d000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:228)
at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:81)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87)
- locked <0x000000073a32d220> (a sun.nio.ch.Util$2)
- locked <0x000000074e332670> (a java.util.Collections$UnmodifiableSet)
- locked <0x00000007426f4b58> (a sun.nio.ch.EPollSelectorImpl)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98)
at
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:259)
at
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
at
org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:604)
at java.lang.Thread.run(Thread.java:722)
at com.electriccloud.util.EcThread.run(EcThread.java:84)
Locked ownable synchronizers:
- None
{noformat}
Google led us to a report of a bug in java 6/7 in the epoll implementation on
linux: https://github.com/netty/netty/pull/565
Is it possible for HttCore to apply a similar approach to avoid this issue?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
