IBM Support

PH24756: WEBSPHERE APPLICATION SERVER JVM START FAILED ON PARSING META-INF/EJB-JAR_MERGED.XML

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

  • The application server fails to start with below exception:
    Caused by:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.Deploy
    mentDescriptorLoadException: META-INF/ejb-jar.xml
    and
    Caused by:
    org.eclipse.jst.j2ee.commonarchivecore.internal.exception.Resour
    ceLoadException: IWAE0007E Could not load resource
    "META-INF/ejb-jar_merged.xml" in archive "ppc-ejb-2.40.2.0.jar"
    and
    Caused by: org.eclipse.emf.common.util.WrappedException:
    java.io.IOException: Stream closed
    Caused by: java.io.IOException: Stream closedAfter restart it
    works.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application start fails with a failure  *
    *                      to                                      *
    *                      process an EJB's deployment descriptor, *
    *                      as described in the APAR description.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In scenarios in which application code can run on a separate
    thread as the application is completing its startup process, it
    is
    possible for a condition to occur in which closure operations on
    the module object collide, causing one of them to fail. The
    specific case that precipitated this APAR involved an EJB timer,
    which fired after the EJB was started but before the full
    completion of all application start operations.
    

Problem conclusion

  • Additional synchronization was added to ensure that the module
    operations are thread-safe.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.18 and 9.0.5.5. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH24756

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-23

  • Closed date

    2020-06-15

  • Last modified date

    2020-06-15

  • 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 APP S

  • Fixed component ID

    5724J0800

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:
16 June 2020