-
Bug
-
Resolution: Fixed
-
P2
-
hs10, 1.4.2_11
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2187235 | 7 | Y. Ramakrishna | P2 | Closed | Fixed | b80 |
| JDK-2190005 | 6u21 | Y. Ramakrishna | P2 | Resolved | Fixed | b01 |
6.0U4 with Xloggc:file, CMS and CMSclassunloading.
The class unloading messages go to stdout rather than the
GC logfile: [Unloading class .....]
Synopsis line changed from:-
"Classunloading messages of CMS go to stdout rather than Xloggc file"
to:-
"Classunloading messages go to stdout rather than Xloggc file, causing hangs when stdout is closed"
better reflecting the issue that the customer is concerned about,
and so as not to give one the misimpression that this was an
issue limited to the CMS collector (which it is not).
The class unloading messages go to stdout rather than the
GC logfile: [Unloading class .....]
Synopsis line changed from:-
"Classunloading messages of CMS go to stdout rather than Xloggc file"
to:-
"Classunloading messages go to stdout rather than Xloggc file, causing hangs when stdout is closed"
better reflecting the issue that the customer is concerned about,
and so as not to give one the misimpression that this was an
issue limited to the CMS collector (which it is not).
- backported by
-
JDK-2190005 Classunloading messages go to stdout rather than Xloggc file, causing hangs when stdout is closed
-
- Resolved
-
-
-
- Closed
-
- relates to
-
-
- Closed
-