IBM Support

PM97149: FAILURE TO ACCESS BINARY FILES DURING APPLICATION DEPLOYMENT SHOULD CAUSE THE DEPLOYMENT TO FAIL.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A failure to access binary files during an application
    deployment is displayed as a warning, but application
    deployment is allowed to proceed.
    
    The DeploymentManager Servant Region showed the following error
    during the deployment process:
    
    ./bbgrjtr.cpp+733 tag= ... Failed to extract binaries to
    temporary location:
     Binaries files were not added!
     This load strategy
    [org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Direct
    oryArchiveLoadStrategyImpl@cf7ab355 ] Container
     [ com.ibm.etools.commonarchive.impl.WARFileImpl@e9192e7d
    (URI:service-interface-1.6.0.4.war, lastModified: 0, size: 0,
    directoryEntry: <unset>, originalURI:
    service-interface-1.6.0.4.war) (types: null)]
    com.ibm.config.eclipse.wtp
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
    ryLoadStrategyImpl.collectFilesFromBinaries
    
    
    A failure to access binary files should cause application
    deployment to fail.
    

Local fix

  • The application deployed fine when the deployment was run
    again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application deployment is allowed to    *
    *                      complete after a "Failed to extract     *
    *                      binaries" warning occurs.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An application deployment is allowed to complete even after
    the deployment processing fails to access binaries content of
    the application.  The result is an incomplete deployment of
    the application.  When application binaries cannot be accessed,
    an application deployment should fail.
    The problem symptom is the presence of a "Failed to
    extract binaries to temporary location: Binaries files were
    not added!" warning message in server log files.  For example:
    ./bbgrjtr.cpp+733 tag= ... Failed to extract binaries
    to temporary location: Binaries files were not added!
    This load strategy
    [org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Direct
    oryArchiveLoadStrategyImpl@cf7ab355 ] Container [
    com.ibm.etools.commonarchive.impl.WARFileImpl@e9192e7d
    (URI:service.war, lastModified: 0, size: 0, directoryEntry:
    <unset>, originalURI: service.war) (types: null)]
    com.ibm.config.eclipse.wtp
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
    ryLoadStrategyImpl.collectFilesFromBinaries
    

Problem conclusion

  • A code update was made to cause the deployment to fail when
    the problem occurs.
    
    The code update is enabled by setting java custom property
    "org.eclipse.jst.j2ee.commonarchivecore.requireBinaries" to
    "true".  By default, a property value of "false" is used.
    When the property value is "false", the "Failed to extract
    binaries" problem causes a warning to be displayed, and the
    deployment is allowed to complete.  When the property value is
    "true", the "Failed to extract binaries" problem causes an
    exception to be generated and caused the deployment to fail.
    
    The default behavior, when the java custom property
    is not explicitly set, is the current behavior, to
    display a warning and allow the deployment to complete.
    
    APAR PM97149 is currently targeted for inclusion in WebSphere
    Application Server V8.5 Fix Pack 8.5.5.3.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM97149

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-09-16

  • Closed date

    2014-03-06

  • Last modified date

    2014-03-06

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022