IBM Support

PI50094: ERROR INITIALIZING AXIS2 JVMSERVER: UNABLE TO DELETE /TMP/AXIS2-TMP-3588079663220691559.TMP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting more than one Axis2 JVMServer in a CICS region a
    a timing issue within the can cause problems with temporary
    file deletion resulting in a NullPointerException being thrown.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: NullPointerException during startup     *
    *                      of an Axis2 JVMSERVER.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During the initialization of an Axis2 JVM server, the Axis2
    framework attempts to delete temporary files created by all
    Axis2 servers on the LPAR.  If 2 or more Axis2 JVM server are
    initializing at the same time there is the potential for a race
    condition during the deletes.  This can cause one of the JVM
    servers to receive a NullPointerException and fail to
    initialize.
    
    Within an Axis2 JVM server the Apache Commons Logging component
    is provided.  This is missing some of the logging implementation
    java classes which could lead to ClassNotFoundExceptions being
    caused during an application execution.
    

Problem conclusion

  • Updated the Axis2 Framework code to correctly handle the
    deletion of files and directories if another process has deleted
    them already.
    
    Updated the common-logging.jar to correctly include all the
    required implementation classes.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PI50094

  • 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 / Xsystem

  • Submitted date

    2015-10-07

  • Closed date

    2016-04-07

  • Last modified date

    2016-05-04

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

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

    PI55129 UI36995

Modules/Macros

  • DFJ@H308 DFJ@H320
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R90D PSY UI36995

       UP16/04/22 P F604

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:
04 May 2016