IBM Support

PI40759: OSGI-BUNDLE IS ACTIVE BEFORE BUNDLEACTIVATOR HAS FINISHED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an active CICS-Bundle is "disabled", "discarded" and then
    new "installed" (e.g. for a bundle-refresh), then the
    OSGi-Bundle will become ACTIVE before the
    BundleActivator-start-method has finished. The main-method of
    that bundle can be called although the start-method of the
    BundleActivator is still in progress. That leads to some
    problems, because the activator prepares the way for that
    bundle. Because of that problem, it is not possible to refresh
    the JAVA-Code in a running CICS-Region.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Able to call CICS-MainClass before      *
    *                      OSGI Bundle Activator has completed.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a CICS BUNDLE containing an OSGi Bundle is installed, the
    CICS-MainClass's within the OSGi Bundle are registered with the
    OSGi framework.  If an Activator is enabled then the
    registration can happen prior to the Activator completing.  This
    allows the CICS-MainClass's to be linked to prior to the OSGi
    Bundle activation completing which could cause errors in the
    executing transaction.
    

Problem conclusion

  • CICS OSGi bundle registration has been updated to only register
    when an OSGi Bundle becomes ACTIVE.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI40759

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-11

  • Closed date

    2015-06-29

  • Last modified date

    2015-08-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UI29053

Modules/Macros

  • DFJ@H352
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R90D PSY UI29053

       UP15/07/10 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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 August 2015