Here is a way shot in the dark and one that probably has nothing to do with it.
I remember a couple of years ago I was working at a company that used eclipse as its main development platform. We implemented some new features that worked great inside of eclipse but would fail on the build. I was told (take with a grain of salt) that eclipse uses the IBM implementation of the JVM and not the Sun version. The two version don't always work the same. As I write this it seems to be more of a configuration issue that probably involves a simple setting hidden 25 menus down that will fix it. Jeremy R. Easton-Marks "être fort pour être utile" On Tue, Oct 6, 2009 at 12:22 PM, Patrick Wright <[email protected]> wrote: > Tom > > Why not run jstack against Eclipse (or the JVM process it is spawning > when you are running your tests)? You could also use VisualVM to do > the same thing--a bit more comfortable to capture and review more > stack traces. You should be able to see where the process is hanging. > > > Regards > Patrick >
