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

Update center get stuck after connection check

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • plugin-proposals
    • None
    • Platform: All, OS: All

      All,
      I'm having some problems updating plugins with a current version of Hudson. I
      tried to update plugins in v268, and in the update center page, it lists the
      plugins I want to update and goes the preparation portion (checking internet,
      java.net) ok, but then none of the hpi files appear to have been downloaded and
      each of the items are stuck in "pending." When I roll back to v262, the plugins
      update as expected. Has anyone else seen this? I'm using Hudson on Windows
      Server 2003 and Tomcat 6.0.18. I don't see anything out of the ordinary in
      either the Hudson log or Tomcat logs. Can I enable something to provide more
      detail on the update center transactions?

      Thanks,
      topher
      ------------------------------------------
      Update center installer thread

      "Update center installer thread" Id=81 WAITING on
      java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@13fde6e

      at sun.misc.Unsafe.park(Native Method)

      • waiting on
        java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@13fde6e
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
        at
        java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)

      at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:358)
      at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:946)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:906)

      at java.lang.Thread.run(Thread.java:619)
      ------------------------------------------
      This stack dump shows that the thread that is responsible for downloads
      and updates is waiting for another job, so is not necessarily an
      indication of anything wrong (or right). I've seen the update center
      page not refreshing itself, so if you see that a download is "stuck in
      pending", it's possible that that the page just failed to reload. If you
      manually refresh the page, does it show an updated status?

      – Dean
      ------------------------------------------
      In my case, no. I've refreshed the page and even enabled auto-refresh. At one
      point, I had a meeting and left it for over an hour, but the hpi never showed up
      on the machine and the status was still pending. I've stopped and started the
      Tomcat service and re-tried it several times. I also removed the
      update-center.json file to see if the file was corrupted somehow and that was
      causing the problem. None of that worked in my set up. This is also not
      related to a specific hpi. I've tried around half dozen with the same result.
      Hopefully, I can get some time this week to determine what build this starts
      failing on. Right now, I can tell you v262 works, so the breaking version is
      between 262(exclusive) and 268(inclusive) and the issue continues in v270. I've
      never had to deal with enabling additional logging, but if there's something
      useful, I'd be happy to do so if you can tell me how.

      Thanks,
      topher
      ------------------------------------------
      Hi all,
      I am trying to install Grails plugin and I have problem. From an unknown reason
      installation process hangs. Preparation phase is successful but pending state is
      never changed to another state. Logs does not show me any clue. Groovy plugin
      was installed without any problem. Any help appreciated.

      Best regards,

      Ales

            Unassigned Unassigned
            dty Dean Yu
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: