PH15593: CWWKE0700W JVM SERVER THREADLIMIT WARNINGS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When starting a Liberty JVM server (ie. EYUCMCIJ), the
  messages.log file is getting filled with numerous CWWKE0700W
  warning messages indicating the CICS thread limit has been
  reached:
  .
   CWWKE0700W: [com.ibm.cics.wlp.threading]
   [CICSThread] @Warning: triggerRealThread() -
     Response: CICS_THREAD_LIMIT, Reason: INTERNAL ERROR, Code: 0
  .
  For the application JVM, increasing the max number of threads
  on the JVM RDO definition seemed to alleviate these messages.
  However, for the EYUCMCIJ JVM server, there is no user-defined
  RDO definition.
  .
  Additional Symptom(s) Search Keyword(s): KIXREVxxx
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: CWWKE0700W CICS_THREAD_LIMIT issued     *
  *                      when a Liberty JVM server is enabled.   *
  ****************************************************************
  When a Liberty JVM server is enabled an empty Java Transaction
  API (JTA) transaction is run to trigger recovery of the units of
  work on the tranlog (if any) from the previous instances of the
  Liberty JVM server.
  This takes place whilst Liberty is initialising its thread pool.
  If Liberty requests that CICS creates the maximum number of
  threads allowed by the JVMSERVER thread limit then CICS will
  reject the last request because the thread running the empty
  JTA transaction is counted by CICS as being part of the limit.
  This causes Liberty to issue a CWWKE0700W message with Response
  CICS_THREAD_LIMIT. Liberty will retry until successful which
  can cause many CWWKE0700W messages to be written to
  messages.log.
  SJ 0B18 THREADLIMIT_REACHED exception trace entries are written
  to the CICS internal trace table.
  
  Keywords: msgCWWKE0700W KE0700W KE0700
  

Problem conclusion

• The way in which JTA recovery is triggered when a Liberty
  JVM server is enabled has been changed to ensure it does not
  cause CWWKE0700W messages to be issued.
  

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:

  UI65975

Modules/Macros

• DFHAPLJ1 DFHAPLJP DFHDSAC  DFHLEPTS DFHPIWR  DFHSJBD  DFHSJDM
  DFHSJDS  DFHSJDUF DFHSJIN  DFHSJIS  DFHSJIX  DFHSJJI  DFHSJJS
  DFHSJL   DFHSJNA  DFHSJNR  DFHSJNT  DFHSJRE  DFHSJRL  DFHSJRM
  DFHSJRT  DFHSJSC  DFHSJSM  DFHSJST  DFHSJTH  DFHSJTHT DFHSJTRI
  DFHSJXM  DFHXMIQ  DFJ@H350 DFJ@H351 DFJ@H352 DFJ@H356 DFJ@H360
  DFJ@H415 DFJ@H426 DFJ@H467 DFJ@H468 DFJ@H480
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R200 PSY UI65975

     UP19/10/25 P F910

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.