| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2159339 | 6u10 | Chris Hegarty | P3 | Resolved | Fixed | b20 |
| JDK-2152940 | OpenJDK6 | Chris Hegarty | P3 | Resolved | Fixed | b01 |
While fixing 4708197 it was noticed that the ThreadGroup.setMaxPriority javadoc asserting that the parent's maximum priority is an upper limit for a new max priority value (if a parent ThreadGroup is defined). But the current ThreadGroup instance max priority is used instead.
- backported by
-
JDK-2152940 (thread) ThreadGroup.setMaxPriority checks against last set maximum, not parent's maximum
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-4708197 (thread) ThreadGroup.setMaxPriority changes priority if param is out of range
-
- Closed
-