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

HTTP requests hang indefinitely after some time running

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Not A Defect
    • Component/s: core
    • Labels:
      None
    • Environment:
      > uname -a
      SunOS jenkins101.demo 5.11 joyent_20131218T184706Z i86pc i386 i86pc Solaris
    • Similar Issues:

      Description

      Jenkins 1.570 (and many previous versions) stop responding to any HTTP requests after running for somewhere between 5 minutes and an hour. Increasing the heap size didn't seem to help, and jmap -heap seems to indicate that there is enough memory available.

      jstack -F (jstack failed without -F) seems to indicate that all the threads are blocked, but I can't tell why Jenkins doesn't respond to HTTP requests, or even if there is anything I can do to fix it other than restarting the entire Java VM.

        Attachments

        1. jmap_heap.txt
          1 kB
        2. jmap-heap.txt
          1 kB
        3. jstack_F.txt
          181 kB
        4. jstack-F.txt
          25 kB
        5. systemInfo.txt
          4 kB

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            What JRE are you using? Are you able to use an Oracle JDK 1.7? If so, does the problem occur there as well?

            Show
            danielbeck Daniel Beck added a comment - What JRE are you using? Are you able to use an Oracle JDK 1.7? If so, does the problem occur there as well?
            Hide
            indirect André Arko added a comment -

            The problem does occur on Oracle JDK 1.7.

            When I opened this ticket, we were using Oracle JDK 1.6:

            Java version "1.6.0_26"
            Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
            Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode)
            

            Today, I upgraded our Jenkins box to Oracle JDK 1.7:

            java version "1.7.0_67"
            Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
            Java HotSpot(TM) Server VM (build 24.65-b04, mixed mode)
            

            We start Jenkins using the jar runner. Here's the full command run:

            /opt/local/java/sun6/bin/amd64/java -Xmx4g -XX:PermSize=192m -XX:MaxPermSize=192m -jar /opt/jenkins/jenkins.war --httpListenAddress=127.0.0.1 --httpPort=8080

            Since I wasn't super specific before, the exact problem is that Jenkins continues to accept HTTP requests, but hangs without writing any bytes until the client times out. I've uploaded the output of the systemInfo page and new dumps from jmap -heap and jstack -F on JDK 1.7.

            Thanks!

            Show
            indirect André Arko added a comment - The problem does occur on Oracle JDK 1.7. When I opened this ticket, we were using Oracle JDK 1.6: Java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Server VM (build 20.1-b02, mixed mode) Today, I upgraded our Jenkins box to Oracle JDK 1.7: java version "1.7.0_67" Java(TM) SE Runtime Environment (build 1.7.0_67-b01) Java HotSpot(TM) Server VM (build 24.65-b04, mixed mode) We start Jenkins using the jar runner. Here's the full command run: /opt/local/java/sun6/bin/amd64/java -Xmx4g -XX:PermSize=192m -XX:MaxPermSize=192m -jar /opt/jenkins/jenkins.war --httpListenAddress=127.0.0.1 --httpPort=8080 Since I wasn't super specific before, the exact problem is that Jenkins continues to accept HTTP requests, but hangs without writing any bytes until the client times out. I've uploaded the output of the systemInfo page and new dumps from jmap -heap and jstack -F on JDK 1.7. Thanks!
            Hide
            indirect André Arko added a comment -

            Hung JVM information from the Oracle JDK 1.7.

            Show
            indirect André Arko added a comment - Hung JVM information from the Oracle JDK 1.7.
            Hide
            evernat evernat added a comment -

            the server memory is full, it's normal that the server stops responding

            Show
            evernat evernat added a comment - the server memory is full, it's normal that the server stops responding

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              indirect André Arko
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: