PH24178: THE CICS BUNDLES WILL BE IN A WRONG STATE (INSTALLED) AFTER JVM RESTART. 20/06/23 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After restarting a Liberty JVM server OSGi bundles installed
  using CICS bundles fail to enable.  messages.log and the JVM
  error file will show:
  
  E CWWKE0701E: [com.ibm.cics.osgi.impl]
  [Controller] @Error: installBundle() - Exception
  java.lang.Exception: Symbolic-name: package.class.name
  Version: 1.0.0 has already been installed.
  
  The bundles need to be discarded before restarting the region
  so that they can be enabled.
  
  To circumvent this problem add the following to the JVM profile:
  
  -Dcom.ibm.cics.jvmserver.wlp.args=--clean
  
  Note, this circumvention may cause the JVM's shared class cache
  to fill up faster.
  
  Additional Symptom(s) Search Keyword(s): KIXREVCHY
  CWWKE0701E installBundle Exception
  

Local fix

• add the following line to JVM profile
  -Dcom.ibm.cics.jvmserver.wlp.args=--clean
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users with PH17642 applied.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICS bundles containing OSGi            *
  *                      applications fail to enable when their  *
  *                      associated Liberty JVM server is        *
  *                      restarted.                              *
  ****************************************************************
  A Liberty JVM server is installed and enabled.  A CICS bundle
  containing at least one OSGi bundlepart that targets the Liberty
  JVM is also installed and enabled.
  
  The Liberty JVM gets restarted.  This could be done by an SPI
  command, recovery after an unexpected error, or when the CICS
  region is restarted.  Due to a change made by PH17642 Liberty is
  no longer started with the -clean option.  This means that the
  previously installed OSGi application is automatically recovered
  from the Liberty workarea as part of the Liberty startup.  CICS
  then tries to install the CICS bundleparts that are associated
  with this JVM.  The OSGi bundlepart from the CICS bundle is
  found to already be installed.  This is unexpected and an
  exception is thrown by com.ibm.cics.osgi.impl.Controller
  (com.ibm.cics.osgi.bundlepart.impl.
   CICSOSGIBundlepartControllerImpl at CICS 5.5 and above).
  The CICS bundle ends up in a disabled state.
  
  There is now a mismatch between the CICS and Liberty state.  The
  CICS bundle is disabled but the OSGi application is actually
  installed and available to run in Liberty.
  

Problem conclusion

• UI67365 UI69615 UI67364 UI69611 UI69409 UI67368 UI67366 UI67367
  UI70124 UI68384 UI69693 UI69694 UI69616
  
  CICS has been changed to issue a warning message to DFHJVMTRC
  (and DFHJVMLOG at 5.5 and above) when a duplicate OSGi
  application has been detected in Liberty.  The associated CICS
  bundle will now be successfully enabled.
  
  The duplicate OSGi application can be removed from Liberty by
  starting Liberty with the -clean option.  To do this, add the
  following to the JVM profile;
  
  -Dcom.ibm.cics.jvmserver.wlp.args=--clean
  
  Note that using --clean will impact Liberty and JVM caching and
  is not recommended to be used permanently.
  
  Or you could disable, discard and then re-enable the BUNDLE
  resource.
  
  At CICS 5.3 and 5.4 this APAR changes the behaviour of JVM
  server logging, after this APAR is applied warning messages will
  now always be written to dfhjvmtrc regardless of the SJ trace
  level set. This may result in warning messages being displayed
  that were not seen before.
  At CICS 5.5 and above LOG_LEVEL can be set on the JVM profile to
  control whether the warning messages are issued or not.
  

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:

  UI70655 UI70656 UI70658 UI70659 UI70660 UI70661

Modules/Macros

• DFHAPJVM DFHAPLJP DFHAXIS2 DFHCAL64 DFHCDJNI DFHCDK64 DFHKETIX
  DFHSJBD  DFHSJDM  DFHSJDS  DFHSJDUF DFHSJIN  DFHSJIS  DFHSJIX
  DFHSJJS  DFHSJL   DFHSJLOG DFHSJNA  DFHSJNDI DFHSJNR  DFHSJNT
  DFHSJPP  DFHSJPTI DFHSJRE  DFHSJRL  DFHSJRM  DFHSJRT  DFHSJSA
  DFHSJSC  DFHSJSM  DFHSJSR  DFHSJST  DFHSJTE  DFHSJTH  DFHSJTRI
  DFHSJWL  DFHSJXM  DFJ@H317 DFJ@H350 DFJ@H351 DFJ@H352 DFJ@H356
  DFJ@H360 DFJ@H387 DFJ@H427 DFJ@H448 DFJ@H467 DFJ@H468 DFJ@H561
  DFJ@H563 DFJDTCOE DFJOUTRE DFJWLPBP DFJWLPPL
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R00D PSY UI70655

     UP20/07/24 P F007 {

• R10D PSY UI70658

     UP20/07/22 P F007 {

• R200 PSY UI70661

     UP20/07/22 P F007 {

• R300 PSY UI70660

     UP20/07/22 P F007 {

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.