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

Dangling socket connections to jenkins after using cli jar?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: cli, core
    • Labels:
      None
    • Environment:
      rhel 5.5
    • Similar Issues:

      Description

      after using CLI in a loop to update dozens or hundreds of jobs, frequently see (lsof) many many open socks to the jenkins.war process and see (netstat) many tcp sockets in TIME_WAIT.

      not sure if I'm interpreting it correctly, but if I am, perhaps

      jenkins / cli / src / main / java / hudson / cli / CLI.java

      might consider using

      http://docs.oracle.com/javase/1.4.2/docs/api/java/net/Socket.html#setSoTimeout%28int%29

      with a reasonable short value (10s?) so that when the client finishes, the jenkins.war process can release resources from its end faster?

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. JENKINS-41745 Remoting-free CLI

          • Major - Major loss of function.
          • Resolved

            Activity

            Ascending order - Click to sort in descending order
            moncreaff Greg Moncreaff created issue -
            rtyler R. Tyler Croy made changes -
            Field Original Value New Value
            Workflow JNJira [ 142633 ] JNJira + In-Review [ 175731 ]
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-41745 [ JENKINS-41745 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              moncreaff Greg Moncreaff
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated: