Uwe Stuehler created JENKINS-13275:
--------------------------------------
Summary: Jenkins stops handling HTTP/AJP requests after some time
Key: JENKINS-13275
URL: https://issues.jenkins-ci.org/browse/JENKINS-13275
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.457 from official package, Debian 6.0.4, x86_64
(amd64)
Reporter: Uwe Stuehler
Priority: Critical
After about a day of normal operation, Jenkins will suddenly stop handling HTTP
and AJP requests. JNLP slave connections are still handled normally, jobs
continue to run and notifications are delivered as usual.
Whenever this happens, we see connections being accept()ed, but the system call
trace reveals that nothing actually happens with the new file descriptor.
jstack output shows 200 {{RequestHandlerThread}} threads with exactly the same
backtrace:
{noformat}
"RequestHandlerThread[#871]" daemon prio=10 tid=0x00007fee8527a800 nid=0xf2c
runnable [0x00007fee7d493000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.DataInputStream.readFully(DataInputStream.java:178)
at java.io.DataInputStream.readFully(DataInputStream.java:152)
at
winstone.ajp13.Ajp13IncomingPacket.<init>(Ajp13IncomingPacket.java:60)
at
winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:170)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:67)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
