IV65160: GC ASSERTION/CRASH DURING JVM STARTUP

APAR status

• Closed as program error.

Error description

• Error Message: 0000000030000500: Object neither in heap nor
  stack-allocated in thread main0000000030000500:
  O-Slot=00000000300146100000000030000500:        O-Slot
  value=00000000300146520000000030000500:
  PC=00000000000000070000000030000500:
  framesWalked=00000000030000500:
  arg0EA=00000000300C30D00000000030000500:
  walkSP=00000000300C30300000000030000500:
  literals=00000000000000800000000030000500:
  jitInfo=00000000000000000000000030000500:
  stack=00000000300BD8C8-00000000300C30D813:02:22.744 0x300f3d00
   j9mm.479    *   ** ASSERTION FAILED ** at
  PartialMarkingScheme.cpp:972:
  ((MM_StackSlotValidator(MM_StackSlotValidator::NOT_ON_HEAP,
  *slotPtr, stackLocation, walkState).validate(_env)))
  .
  Stack Trace: N/A
  .
  

Local fix

Problem summary

• The JVM may crash or assert very early during startup.
  

Problem conclusion

• The JVM has been updated to prevent this issue.
  .
  This APAR will be fixed in the following Java Releases:
     7    SR8       (7.0.8.0)
     7 R1 SR2       (7.1.2.0)
     6    SR16 FP2  (6.0.16.2)
     6 R1 SR8 FP2   (6.1.8.2)
  .
  Contact your IBM Product's Service Team for these Service
  Refreshes and Fix Packs.
  For those running stand-alone, Java maintenance is available
  from:
             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

• R260 PSY

     UP

• R270 PSY

     UP

• R600 PSY

     UP