IBM Support

IT08820: LOCKED JAVA FILES CAN CAUSE DEPLOYMENT FAILURE ON WINDOWS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Java code can lock Java files that have been deployed to an
    integration server, such as JAR files, or property files within
    JAR files. If those locks are not released by the same Java
    code during undeployment or redeployment, then on Windows
    systems that deployment will fail with a BIP4502E error message.
    Use of log4j can lead to this situation, when log4j files
    (either JAR files or property files) are deployed to the
    integration server, and log4j is not properly shut down.
    

Local fix

  • Ensure that all locks on deployed Java files are released when
    the onDelete method is called for JavaCompute nodes.
    If a deployed copy of log4j is in use, then log4j can be
    shutdown from the onDelete method by calling
    org.apache.log4j.LogManager.shutdown();
    Alternatively, the files that are being deployed and locked can
    be placed in the shared-classes directory instead of deploying
    them inside of a BAR file.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus deploying Java code to
    integration servers.
    
    
    Platforms affected:
    Windows on x86-64 platform, Windows on x86 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    It is possible for Java code to acquire and maintain a file lock
    on deployed JAR files. One example of third-party code which
    performs this type of action is Log4j. If log4j is used in a
    JavaCompute Node (JCN) and is not shut down properly from the
    onDelete() method of a JCN, then it can maintain a file lock on
    a deployed JAR file that contains either log4j itself or the
    log4j configuration. When this file lock is in place, a
    redeployment of those JAR files on Windows may fail and be
    rolled back with the following error messages:
    
    BIP4502E: An unexpected error occurred during the deployment of
    a Java
    resource.
    
    An error occurred during the deployment of a Java resource. This
    may
    have left the broker in an inconsistent state.
    
    Ensure there is sufficient disk space available on the machine
    running
    the broker runtime. Stop the broker, delete all files in
    '...\JAR\', restart the broker and perform a full redeploy.
    
    BIP4395E: Java exception: 'java.nio.file.FileSystemException';
    thrown
    from class name: 'sun.nio.fs.WindowsException', method name:
    'translateToIOException', file: 'WindowsException.java', line:
    '98'
    
    The message contains that data associated with a Java exception.
    
    No user action required.
    
    The only way to redeploy these JAR files is to restart the
    integration server, which releases the file locks on the
    deployed JAR files. Alternatively, the deployed Java code can be
    corrected to release the file locks during
    redeployment/undeployment by providing an onDelete() method in a
    JavaCompute node.
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0. For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product has been modified so that the locked JAR files are
    truncated to zero-bytes when they cannot be deleted or renamed.
    This may result in leftover zero-byte JAR files deployed to the
    integration server when those JAR files are undeployed.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.5
    v10.0      10.0.0.2
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT08820

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-11

  • Closed date

    2015-09-11

  • Last modified date

    2015-09-11

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

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

Fix information

  • Fixed component name

    INTEGRATION BUS

  • Fixed component ID

    5724J0530

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020