IJ32296: JVM TAKES MORE TIME TO START UP

APAR status

• Closed as program error.

Error description

• Error Message: In one of the test scenarios, the Java startup
  time was increased from 3.0 seconds to 3.4 seconds.
   This issue only applicable to GC policy gencon and
  optavgpause.
  .
  Stack Trace: N/A
  .
  

Local fix

• The issue can be worked around by setting the initial heap value
  (-Xms) as the same value as the maximum heap value (-Xmx).
  

Problem summary

• The problem is caused when a trigger point of the end of the
  final STW GC event is mistakenly removed.
  

Problem conclusion

• The trigger point of the end of the final STW GC event is put
  back.
  
   https://github.com/eclipse/omr/pull/5911
  
  
  .
  This APAR will be fixed in the following Java Releases:
   8 SR6 FP30 (8.0.6.30)
  .
  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