Please reopen and post a thread dump.

Happening to me on 1.480.2

Rackspace centos 5.8 machine.
4GB ram machine.

Latest jetty. https

Build working perfectly, but find bugs is stuck.

java 1.6
ant 1.8

@michael: please attach a thread dump. How many warnings do you have?

How do I produce a thread dump?

Each machine is a 2 CPU machine in the rackspace cloud

centos 5.8
java 1.6
ant 1.8

I have swapped between 1 and 2 executors.

How many findbugs files are you parsing? How many warnings are in these files?

From the log I see that the findbugs library connects to the internet to resolve XML entities. I'll have a look at the library to see if that can be suppressed...

@michael can you please also attach the findbugs result file? Then I can see in the debugger where these entities are actually resolved. In my findbugs results files there are no entity references.

We did a reset and the data is gone.
Let me look at our setup.

We have findbugs configured outside of Jenkins. It is in our ant files. Maybe you are finding an old Jar file we already have on the system, or we have some old something the Jenkins findbugs is finding.

I'll look at things on my side.

It's 19+ hours for us (didn't wait till completion, cancelled the build): JENKINS-17949.

Please attach your files so I can try to reproduce...