IBM Support

PI76439: APPLICATION CLIENT MODULE CREATED WHEN EMPTY "MAIN-CLASS:" FOUND IN MANIFEST.MF OF JAR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An extraneous "Main-class:" attribute with no class specified
    will cause the application server to configure the JAR as an
    application client module during deployment.
    It also adds the empty class name to the list of classes to be
    searched for annotations.
    This results in the following warning message in the log file.
    
    16/11/10 13:34:38:157 JST  00000053 annotations   W
    com.ibm.ws.amm.scan.context.ScannerContextImpl
    getInputDataForClass Failed to open resource " .class " from
    module
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Warning message "Failed to open         *
    *                      resource " .class " from module "       *
    *                      moduleName.jar " is seen during         *
    *                      application deployment.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when the MANIFEST.MF file of a JAR contains
    a "Main-class:" attribute without a class name.  The
    application server incorrectly uses a single space as the
    class name; " .class".  The warning message occurs during
    annotation scanning because the class is not found.
    The presence of the "Main-class:" attribute also causes the
    JAR to be configured as an application client module, but
    since no actual main class name is provided the module cannot
    be launched.
    

Problem conclusion

  • The code has been modified so that an empty "Main-class:"
    attribute provides the same result as if no "Main-class:"
    attribute were specified in the MANFEST.MF.
    
    A JAR with a MANIFEST.MF containing an empty "Main-class:" will
    not be configured as an application client module unless it
    also contains an application-client.xml file.
    
    A warning message will still be generated, but it will more
    correctly reflect the actual problem:
    "Main-class: attribute found in manifest.mf without a value.
    Setting Main class to null."
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.14, 8.5.5.12, 9.0.0.4.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI76439

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-10

  • Closed date

    2017-03-28

  • Last modified date

    2017-03-28

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 June 2020