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

Job build freezes during access to svn repository

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major Major
    • svncompat14-plugin
    • None

      Environment:
      Jenkins version 1.499
      Jenkins Subversion Plug-in 1.44
      many other plugins.

      Description:
      Time to time (30% percent of the total builds number) builds stuck.

      Notes:
      Problem always at the stage of working with svn repository (f.e. check update).
      Access to the svn repository from this host is available.
      Tasks can not be stopped (till Jenkins full restart)
      After Jenkins restart the task is performed

      job logs looks like:

      • example 1:
        Started by user A
        Building in workspace /home/A/.jenkins/api_functional
        *loader icon*
        
      • example 2:
        Started by user B
        Building in workspace /home/A/.jenkins/page_response_status_code
        Reverting /home/A/.jenkins/page_response_status_code/.
        Updating svn://path/qa to revision '2013-01-21T14:23:55.881 +0400'
        *loader icon*
        

      threadDump has been attached

      Additional information:

      Current SCM Polling Activities
      There are more SCM polling activities scheduled than handled, so the threads are not keeping up with the demands. Check if your polling is hanging, and/or increase the number of threads if necessary.

      The following polling activities are currently in progress:
      Project ↓ Running for
      API functional 46 min
      Page response status code 1 hr 16 min

          [JENKINS-16427] Job build freezes during access to svn repository

          kutzi added a comment -

          kutzi added a comment - Could be related to http://issues.tmatesoft.com/issue/SVNKIT-312 Can you try the workarounds described here? http://issues.tmatesoft.com/issue/SVNKIT-312#comment=60-4367

          taskoma added a comment -

          Hello kutzi, thanks for you answer
          Looks very similar. Now I disabled keyring through ~/.subversion/config and try reproduce the problem.

          additional question about first recipe:

          1. You can disable Keyring for every instance of your program by passing the following system variable:
          -Dsvnkit.library.gnome-keyring.enabled=false

          Is it enough run jenkins like

          java -Dsvnkit.library.gnome-keyring.enabled=false -jar jenkins.war
          

          ?

          taskoma added a comment - Hello kutzi , thanks for you answer Looks very similar. Now I disabled keyring through ~/.subversion/config and try reproduce the problem. additional question about first recipe: 1. You can disable Keyring for every instance of your program by passing the following system variable: -Dsvnkit.library.gnome-keyring.enabled=false Is it enough run jenkins like java -Dsvnkit.library.gnome-keyring.enabled=false -jar jenkins.war ?

          kutzi added a comment -

          I don't know. Depending on how you start your job.

          kutzi added a comment - I don't know. Depending on how you start your job.

          taskoma added a comment -

          kutzi, thanks for you comment about problem in svnkit with gnome-keyring !
          Looks like all works ok after modification in subversion config file

          taskoma added a comment - kutzi , thanks for you comment about problem in svnkit with gnome-keyring ! Looks like all works ok after modification in subversion config file

          taskoma added a comment -

          So, it's look like problem in external library, not in Jenkins.

          taskoma added a comment - So, it's look like problem in external library, not in Jenkins.

            swiest Simon Wiest
            taskoma taskoma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: