Bamboo hangs whenever there is a problem with source retrieval

XMLWordPrintable

    • Type: Bug
    • Resolution: Unsolved Mysteries
    • Priority: High
    • None
    • Affects Version/s: 1.0.2
    • None
    • Environment:

      Bamboo 1.0.2, Subversion repo on SourceForge, CVS repo on SourceForge, CVS repo on Java.net

      Bamboo appears to be hanging quiet often (every couple of hours) for the Spring project builds at http://build.springframework.org:8085. The build is manifest as the CPU pegging to 100% and the servlet container not returning pages to users (leaving the connection open). Typically a restart helps this problem. When the logs are checked we the following error:

      007-03-21 03:28:46,958 WARN [Timer-0] [ThreadPoolAsynchronousRunner] com.mchange.v2.async.ThreadPoolAsynchronousRunner$DeadlockDetector@1999a3d
      – APPARENT DEADLOCK!!! Creating emergency threads for unassigned pending tasks!
      2007-03-21 03:29:20,513 ERROR [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] Failed to get the build source code
      com.atlassian.bamboo.repository.RepositoryException: Spring LDAP - trunk
      at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:376)
      at com.atlassian.bamboo.build.strategy.PollingBuildStrategy.requiresBuild(PollingBuildStrategy.java:126)
      at com.atlassian.bamboo.build.DefaultBuildChangeDetector.checkIfBuildNeedsBuilding(DefaultBuildChangeDetector.java:166)
      at com.atlassian.bamboo.build.DefaultBuildChangeDetector.doTask(DefaultBuildChangeDetector.java:114)
      at com.atlassian.bamboo.build.DefaultBuildChangeDetector.run(DefaultBuildChangeDetector.java:77)
      at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
      at java.lang.Thread.run(Thread.java:595)
      Caused by: org.tmatesoft.svn.core.SVNException: svn: PROPFIND request
      failed on '/svnroot/springframework/spring-ldap/trunk'
      svn: Remote host closed connection during handshake
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:48)
      at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:124)
      at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:197)
      at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:160)
      at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:147)
      at com.atlassian.bamboo.repository.svn.SvnRepository.getChangesSinceLastBuild(SvnRepository.java:327)

      From this stack it appears that the connection to the SVN repo at SourceForge is timing out. We see this as users a bit, so while unfortunate, it's not uncommon.

      It's important to note that this isn't limited to just the LDAP project, all of our projects get this issue at various times. In fact, we see it on the SF SVN projects, an analogous error on SF CVS projects, and an error on java.net CVS projects.

      As I said earlier, we're running into this problem every couple of hours. We really like the Bamboo product and are using it heavily, but this issue prevents us from publicizing our use of it and recommending it to others.

        1. bamboo-logs.zip
          6.62 MB
        2. console-output.txt.zip
          409 kB
        3. log-c3p0-args.zip
          281 kB

            Assignee:
            edwin
            Reporter:
            Ben Hale
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: