APAR status
Closed as program error.
Error description
Error Message: ** ASSERTION FAILED ** at ./StandardAccessBarrier.cpp . Stack Trace: N/A . This issue can only happen on z/OS 2.3 or z/OS 2.2 with APAR OA51643
Local fix
Using gc policies other than concurrentScavenge will solve the problem.
Problem summary
In concurrentScavenge, any read of a Java object should be protected by a read barrier so that GC will update the pointer to the object once it has gone stale. The JIT compiler failed to emit read barriers when reading java objects, resulting a stale pointer in the stack, thus causing the GC to crash during stack walk.
Problem conclusion
The JIT compiler has been updated to emit the missing read barriers when reading Java objects. . This APAR will be fixed in the following Java Releases: 8 SR5 FP10 (8.0.5.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
IJ04250
Reported component name
JIT
Reported component ID
620700124
Reported release
130
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-19
Closed date
2018-02-19
Last modified date
2018-02-19
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
JIT
Fixed component ID
620700124
Applicable component levels
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBA","label":"Just In Time (JIT) Compiler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"130","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
19 February 2018