IJ08503: ASSERTION IS HIT DUE TO UNEXPECTED STACK HEIGHT IN DEBUGGING MODE

APAR status

• Closed as program error.

Error description

• Error Message: Customer is getting an assert when running in FSD
  mode after setting a break point:
  j9codertvm(j9ji.104 * ** ASSERTION FAILED ** at decomp.cpp:584:
  (((IDATA)pendingStackHeight >= 0))"
  .
  Stack Trace:
  {getPendingStackHeight__FP10J9VMThreadPUcP8J9MethodUl}
  {libj9jit29.so}{initializeOSRFrame__FP10J9VMThreadP9J9OSRData}
  {libj9jit29.so}{initializeOSRBuffer__FP10J9VMThreadP11J9OSRBuffe
  rP9J9OSRData}
  {libj9jit29.so}{addDecompilation__FP10J9VMThreadP16J9StackWalkSt
  ateUl}
  {libj9jit29.so}{decompileAllFrameIterator__FP10J9VMThreadP16J9St
  ackWalkState@AF63_53}
  {libj9vm29.so} {walkFrame}
  .
  

Local fix

Problem summary

• The problem happens when Java program transfer its execution
  from the JIT compiled code to the interpreter at the monitor
  enter of an inlined synchronized method. The interpreter expects
  a different stack height than the one describe by the JIT
  compiled code.
  

Problem conclusion

• The JIT compiled code has been fixed to make sure the stack
  shape is consistent with what the interpreter expects.
  .
  This APAR will be fixed in the following Java Releases:
   8 SR5 FP21 (8.0.5.21)
  Except with z/OS where this APAR is fixed in:
   8 SR5 FP22 (8.0.5.22)
  .
  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:

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels