-
Bug
-
Resolution: Fixed
-
P3
-
5.0u11, 5.0u8
-
b01
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2176985 | 7 | Y. Ramakrishna | P3 | Closed | Fixed | b17 |
| JDK-2172078 | 6u10 | Y. Ramakrishna | P3 | Resolved | Fixed | b09 |
| JDK-2161160 | 5.0u15-rev | Poonam Bajaj Parhar | P3 | Resolved | Fixed | b09 |
| JDK-2151506 | 1.4.2_16 | Poonam Bajaj Parhar | P2 | Closed | Not an Issue | |
| JDK-2148180 | hs11 | Y. Ramakrishna | P5 | Closed | Fixed | b03 |
low-yield abortable preclean cycles hoing on for a rather long time.
The option CMSMaxAbortablePrecleanTime defaults to a number like
1000 ms or such, so the user ends up being confused as to why
the cycles take so much longer without being cut off at the
default maximum value.
- backported by
-
JDK-2161160 CMS: excessively long abortable preclean cycles
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
JDK-5025281 Allow System.gc() to trigger concurrent (not stop-the-world) full collections
-
- Resolved
-