OA67874: TERMINATION OF MONITORED JVM SERVER PRECEDED BY KJJXCALL ABENDS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Abends in OMEGAMON JVM cross-memory module KJJXCALL are not
  properly recovered.  This may lead to additional abends and
  termination of the monitored JVM server
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IBM Z OMEGAMON AI for JVM, V6.1.0        *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Program exceptions in KJJXCALL may   *
  *                      abnormally terminate JVM servers.       *
  *                      2. OMEGAMON AI for JVM JVMTI agent may  *
  *                      crash in low-memory due to unhandled    *
  *                      allocation failures in                  *
  *                      KJJ_BinaryPayload.                      *
  *                      3. Potential memory leak in GC agent.   *
  *                      4. Group-level zoom in z/OS Connect API *
  *                      Provider Plex View results in missing   *
  *                      API name and Method fields.             *
  *                      5. IBM Z OMEGAMON AI for JVM historical *
  *                      workspaces reflect history only for the *
  *                      current JVM instance.                   *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  *                                                              *
  ****************************************************************
  1. Cross memory abends and/or program exception abends may
  occur in KJJXCALL leading to abnormal termination of the
  monitored JVM server.
  2. KJJ_BinaryPayload uses the new operator without checking
  for allocation failure, causing uncaught exceptions and
  crashes.
  3. Shared static state leads to data corruption and memory
  leaks when GC events run in parallel.
  4. Exception Details lack API and Method info when zoomed
  at group level due to unified display logic.
  5. Historical data views for prior instances is not accessible
  to users.
  

Problem conclusion

• 1. The code was amended to catch abends in KJJXCALL using
  condition handler.
  2. The code was updated to safely detect allocation failures
  and avoid crashes.
  3. Using thread-local storage for GC event data isolates
  threads, preventing corruption and leaks.
  4. Implemented separate views based on zoom level to
  correctly show relevant details.
  5. Access individual component history from the Completed
  Job History. For this purpose, a corresponding menu item was
  added for this workspace.
  

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:

  UJ97634

Modules/Macros

• KJJ      KJJAGENT KJJCPUD  KJJEJS   KJJENVE  KJJGCD   KJJHELHS
  KJJHLSRV KJJHSEL  KJJJSM1  KJJJSUM  KJJLAG31 KJJLAG64 KJJLCK
  KJJLIB   KJJLIB64 KJJLIC   KJJNMVM  KJJNMZ   KJJPLEX  KJJSERV
  KJJTHD   KJJZCDA  KJJZCDD  KJJZCDF  KJJZCES  KJJZCFLT KJJZCSA
  KJJZFLTE KJJZFLTP KJJZPLX  KJJZPLX1 KJJZPLX2 KJJZPLXZ KJJZRES
  KJTCPU   KJTJJOB  KJTMAIN  KJTQMGR
  

Fix information

• Fixed component name

  OM JVM BASE

• Fixed component ID

  5698ABA00

Applicable component levels

• R610 PSY UJ97634

     UP25/07/19 P F507

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.