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

HTTP requests hang indefinitely after some time running

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • core
    • None
    • > uname -a
      SunOS jenkins101.demo 5.11 joyent_20131218T184706Z i86pc i386 i86pc Solaris

      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.

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

          [JENKINS-23863] HTTP requests hang indefinitely after some time running

          André Arko created issue -
          Daniel Beck made changes -
          Component/s New: core [ 15593 ]
          Component/s Original: gui [ 15492 ]
          Labels Original: gui jenkins
          André Arko made changes -
          Attachment New: jmap_heap.txt [ 26622 ]
          Attachment New: jstack_F.txt [ 26623 ]
          Attachment New: systemInfo.txt [ 26624 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-24357 [ JENKINS-24357 ]
          evernat made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 156727 ] New: JNJira + In-Review [ 195486 ]

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

              Created:
              Updated:
              Resolved: