PH22887: JVMSERVER HANG AT THE STATE OF BEING ENABLED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• For CICS 5.4 Liberty JVM, sometimes it hangs at the state of
  Being Enabled.
  
  Jvm(xxxxxxx ) Dis Prf(xxxxxxx ) Ler(DFHAXRO
  ) BEING ENABLED
  Threadc(000) Threadl( 100 ) Cur(0)
  
  
  Additional Symptom(s) Search Keyword(s): KIXREVCHY
  JVMSERVER Being Enabled hang
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A Liberty JVMSERVER hangs in BEING      *
  *                      ENABLED when the JVM fails to           *
  *                      initialise.                             *
  ****************************************************************
  A Liberty JVMSERVER is being enabled. CJSR calls DFHSJTH
  SET_WLP_MAXTHREADS to set the thread limit in Liberty.
  SET_WLP_MAXTHREADS tries to attach a system thread in the JVM,
  but JVM failed to initialise.  As a result the call never
  completes and the JVMSERVER becomes stuck in BEING ENABLED.
  
  The JVMSRVLK is held which prevents all other attempts to change
  the state of the JVMSERVER.
  

Problem conclusion

• CICS has been changed to allow SET_WLP_MAXTHREADS to time out.
  
  The CICS Transaction Server for z/OS V5.4 and V5.5
  Knowledge Center will be updated as follows:
  
  In 'DFHSJnnnn messages' section, new message DFHSJ0938 is added
  as follows:
  
  DFHSJ0938 date time applid userid The Liberty Server has failed
  to start for JVMSERVER jvmserver. Further information may be
  available in JVM STDERR.
  
  Explanation
  A problem has been detected resulting in the Liberty JVM
  failing to start. Look in messages.log and STDERR to determine
  the cause of the problem.
  
  System Action
  The JVM server will be disabled.
  
  User Response
  Review messages.log and STDERR log for any messages that may
  have been issued prior to the failure. The location of the
  STDERR file is defined in the JVM profile.
  
  Module
  DFHSJJS
  
  Message inserts
  1. date
  2. time
  3. applid
  4. userid
  5. jvmserver
  
  Destination
  TDQ.
  

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:

  UI69692 UI69693 UI69694 UI69695 PH26652

Modules/Macros

• DFHAMSJ  DFHAPJVM DFHAPLJP DFHAXIS2 DFHCAL64 DFHCDJNI DFHCDK64
  DFHEIQSY DFHKETIX DFHMESJC DFHMESJE DFHMESJK DFHPIWR  DFHSJBD
  DFHSJDM  DFHSJDS  DFHSJDUF DFHSJIN  DFHSJIS  DFHSJIT  DFHSJIX
  DFHSJJS  DFHSJJST DFHSJL   DFHSJLOG DFHSJNA  DFHSJNDI DFHSJNR
  DFHSJNT  DFHSJPP  DFHSJPTI DFHSJRE  DFHSJRL  DFHSJRM  DFHSJRT
  DFHSJSA  DFHSJSC  DFHSJSM  DFHSJSR  DFHSJST  DFHSJTE  DFHSJTH
  DFHSJTRI DFHSJWL  DFHSJXM  DFHSTP   DFHXMIQ  DFJ@H317 DFJ@H350
  DFJ@H352 DFJ@H356 DFJ@H360 DFJ@H427 DFJ@H467 DFJ@H468 DFJDTCOE
  DFJOUTRE DFJWLPBP DFJWLPPL
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R100 PSY UI69692

     UP20/05/28 P F005

• R103 PSY UI69694

     UP20/05/29 P F005

• R10D PSY UI69693

     UP20/05/29 P F005

• R200 PSY UI69695

     UP20/05/29 P F005

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.