Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13275

Jenkins stops handling HTTP/AJP requests after some time

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • None
    • Jenkins 1.457 from official package, Debian 6.0.4, x86_64 (amd64)

      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:

      "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)
      

          [JENKINS-13275] Jenkins stops handling HTTP/AJP requests after some time

          evernat added a comment -

          Is it reproduced with a recent Jenkins version?

          evernat added a comment - Is it reproduced with a recent Jenkins version?

          Marc Günther added a comment -

          Actually I don't know, back then we switched from using ajp to http, which fixed the problems for us. We never tried ajp again.

          Marc Günther added a comment - Actually I don't know, back then we switched from using ajp to http, which fixed the problems for us. We never tried ajp again.

          evernat added a comment - - edited

          Because Jenkins uses Jetty now instead of Winstone, as embedded container, this was probably fixed.
          Please reopen if not.

          evernat added a comment - - edited Because Jenkins uses Jetty now instead of Winstone, as embedded container, this was probably fixed. Please reopen if not.

            Unassigned Unassigned
            ustuehler Uwe Stuehler
            Votes:
            4 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: