EVALUATION

Fixed via 5.0u15-rev-b09
                                     

EVALUATION

Upon further examination of the code in 5uXX, we realize that though
the workaround may be adequate in some situations, it may not be
in other situations. For such cases, we will need to fix the
use of the timer; see my entry in the comments section
made on 7/19/2007.
                                     

WORK AROUND

There are situations in which the above workaround will
not be very effective. In such cases, use
-XX:CMSMaxAbortablePrecleanLoops=<small number, like 10>.

But see also 6572569 for possible side-effects of this
in certain heap shapes/configurations.
                                     

SUGGESTED FIX

See comments section.
                                     

WORK AROUND

-XX:CMSMaxAbortablePrecleanTime=1 (or 10) or other suitable value, interpreted in
seconds. Note that *this is a temporary workaround*, see comments section.

In particular, *when you upgrade to 5u15* where this bug was
fixed, or to *6.0* or later, please make sure to
*remove* this temporary workaround. In JVM's where this
bug has been fixed, the argument to the CMSMaxAbortablePrecleanTime
is interpreted in *milliiseconds". It's only in JVM's where the
bug is not fixed that it's interpreted as *seconds* and requires
the explicit workaround listed above.
                                     

EVALUATION

See comments section. Fix understood; workaround available (see workaround section).