IV76898: HEALTH CENTER VERSION 3.0 CREATES THREADS THAT ARE NOT ZAAP ENABLED

APAR status

• Closed as program error.

Error description

• Health Center version 3.0 creates threads that are not zaap
  enabled, causing greater general processor usage.  The cpu
  usage can be seen when running with -Xhealthcenter enabled
  when running with any Version 3.0 instance of health center.
  The version of the health center agent is displayed within the
  INFO message at jvm startup when -Xhealthcenter is used. For
  example:
  INFO: Agent version "3.0.4.20150622"
  

Local fix

• remove  -Xhealthcenter to eliminate the general CPU usage
  attributable to the health center agent threads.
  

Problem summary

• The problem was that Health Center threads changed from being
  zAAP-eligible in v2 to zAAP-ineligible in v3.
  

Problem conclusion

• The Health Center and JVM are updated to enable
  Health Center threads to be eligible for dispatch on z/OS
  special processors (zIIP and zAAP)
  z/OS APAR OA49088 MUST ALSO be installed in conjunction
  with this fix to enable the offload capability.
  .
  This APAR will be fixed in the following Java Releases:
     6 R1 SR8 FP20  (6.1.8.20)
     7    SR9 FP30  (7.0.9.30)
     7 R1 SR3 FP30  (7.1.3.30)
     8    SR2 FP10  (8.0.2.10)
  .
  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:

  PI54075

Fix information

• Fixed component name

  J9 COMMON CODE

• Fixed component ID

  620700127

Applicable component levels

• R260 PSY

     UP

• R270 PSY

     UP