IJ41381: ASSERTION FAILURE AT STANDARDACCESSBARRIER.CPP WHEN -XGC:CONCURRENTSCAVENGE IS SET

APAR status

• Closed as program error.

Error description

• Error Message: Assertion failure when -Xgc:concurrentScavenge is
  set.
  readObject ... in Evacuate
  j9mm.141 * ** ASSERTION FAILED ** at
  StandardAccessBarrier.cpp:861: ((false))))
  .
  Stack Trace: #10 javaTrace ()
  #11 MM_StandardAccessBarrier::preObjectRead(J9VMThread*,
  J9Object*, unsigned int*) ()
  #12 jitSoftwareReadBarrier ()
  #13 runJavaThread ()
  .
  

Local fix

• This issue can be worked around using the
  -XXgc:softwareRangeCheckReadBarrier option.
  

Problem summary

• Concurrent Scavenger might have incorrect settings for GS
  support on machines with Guarded Storage HW (z14+) available if
  Concurrent Scavenger is used with Portable AOT or CRIU support.
  

Problem conclusion

• The solution is to ensure that the function that checks whether
  the read barrier is enabled or not, returns true when hardware
  read barriers are disabled.
  https://github.com/eclipse-openj9/openj9/pull/15610
  https://github.com/eclipse/omr/pull/6625
  .
  This APAR will be fixed in the following Releases:
  .
  IBM SDK, Java Technology Edition
   8 SR7 FP16 (8.0.7.16)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, information about the available
  maintenance can be found at:
   https://www.ibm.com/support/pages/java-sdk
  

Temporary fix

Comments

APAR Information

• 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