Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This document attempts to explain what information we need to fix the build hang problem, if you experience one.

  • Go to http://yourserver/threadDump and obtain the thread dump of the Hudson server. If the build is stuck somewhere, the thread call stacks displayed here would help. There's one to one correspondence between the executor and a thread, so say if your build is carried out by executor "foobar #5", look for a thread with this name (but really, if you send it to us, please just send all the thread dumps)
  • If the build is running on a slave called 'xyz', go to http://yourserver/hudson/computer/xyz/systemInfo and obtain the thread dump of the slave agent. If the build is stuck due to some issue on the agent side, this would tell us where it is.
  • I/O in Java is fundamentally synchronous and non-interruptible. So if a build is blocked inside Hudson while performing an I/O (for example, reading from the network), there's just no way to kill such a thread. Check the thread dump in the 1st step and see if that's the case. That said, even if you find this to be the case, please report it to us so that we know where this problem tends to happen (which might allow us to replace such non-interruptible I/O with an interruptible I/O.)

* 2010-09-16: attached master and 2 slave thread dumps (hhuynh) Archiving stuck has been a daily problem for us. We are force to restart Hudson when this happens. It would be great if the archiving has some timeout or taken into account as build time so that the build can move on

  • No labels