ThreadLists fails with a "inconsistent results" error in nightly testing in the GC baselines. Here's an example:

http://gtee.sfbay/gtee/results/MUSTANG/NIGHTLY/VM-MAIN/2007-08-23/GC_Baseline-Xconc/vm/linux-amd64/server/mixed/vm-linux-amd64_server_mixed_MM_REGRESSION2007-08-23-21-14-59/java/lang/management/ThreadMXBean/ThreadLists.jtr

From Swamy:

Date: Thu, 23 Aug 2007 18:50:41 -0500
From: Swamy V <###@###.###>
To: Tony Printezis <###@###.###>,
    Serviceability Group <###@###.###>
Subject: Re: MM_REGRESSION

5. GetThreadLists:
        Failure is reproducible using vmoption -XX:+UseConcMarkSweepGC
        flag.
                ThreadGroup.activeCount() returned 5
                ThreadMXBean.getThreadCount() returned 6

        I suspect ThreadMXBean is returning an extra thread which
        may not be part of main threadGroup. This happens only
        if we use the above mentioned vm option. Does this create
        any java thread?
                Also the ThreadGroup.activeCount() doc says the return
        value may be imprecise and it should be used for informational
        purpose only. So I suspect this could be a test bug.

        But I would like to find out what was the sixth java thread
        which is not visible to ThreadGroup.activeCount().