APAR status
Closed as program error.
Error description
Error Message: N/A . Stack Trace: N/A .
Local fix
The only way to know the number of active threads is to look at the "gcthreads" value at the start of the gc log. If the number of gc threads is reduced before a gc, it will be recorded as a trace. This trace can be obtained by adding the option -Xtrace:print{j9mm.536-537,j9mm.654}
Problem summary
The problem is that the number of active threads can have a significant impact on garbage collector performance, and it is essential to have in the verbose:gc log.
Problem conclusion
The <gc-end> tag now has an additional "activeThreads" property, which records the actual number of garbage collector threads used in each gc. . This APAR will be fixed in the following Java Releases: 8 SR1 FP10 (8.0.1.10) 7 R1 SR3 FP10 (7.1.3.10) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Temporary fix
Comments
APAR Information
APAR number
IV73639
Reported component name
J9 COMMON CODE
Reported component ID
620700127
Reported release
270
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-05-27
Closed date
2015-05-27
Last modified date
2015-05-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
J9 COMMON CODE
Fixed component ID
620700127
Applicable component levels
R270 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]
Document Information
Modified date:
21 February 2022