IJ24740: CRASH FROM GC AFTER CALLING WRITE BARRIER

APAR status

• Closed as program error.

Error description

• Error Message: A GPF is received when some JIT method is
  compiled.
  .
  Stack Trace: The native stack trace may looks like this:
  #13 <signal handler called>
  #14 isObjectInEvacuateMemory ()
  #15 MM_StandardAccessBarrier::preObjectRead ()
  #16 0x00007f60557c5863 in
  MM_ObjectAccessBarrier::mixedObjectReadObject ()
  #17 0x00007f6055e52bb8 in
  TR_J9MutableCallSite::findCallSiteTarget()
  .
  

Local fix

• This issue can be worked around by using -Xgcpolicy:gencon
  

Problem summary

• The write barrier code assumes GC policy Gencon but it might
  fail with Optthruput or Optavgpause.
  

Problem conclusion

• The JVM has been updated so that GC checks for GC policy for
  correct action.
  
  .
  This APAR will be fixed in the following Java Releases:
   8 SR6 FP5 (8.0.6.5)
  .
  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 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