IBM Support

PI91760: CLASSES ARE MISSING IN THE ADMINISTRATIVE CONSOLE AFTER EAR DEPLOYMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After deploying a Maximo EAR and the Save is finished, if we
    start the JVM to which the EAR was deployed immediately after
    the Node says it is back in sync, the application will fail to
    start with complaints about missing classes. But, the problem
    is not missing classes; the problem is that the node is still
    distributing the application. The node should not
    have reported itself synchronized if it is still working to
    deploy the application. There were nearly 82 seconds between
    when the node reported itself as synchronized and when
    it finally finished distributing the application.
    

Local fix

  • Customer needs ifix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using the administrative console to  *
    *                  rollout application updates to clusters.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The console tries to start              *
    *                      applications when the expansion may     *
    *                      not have completed causing the          *
    *                      application not to start.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The administrative console code was not correctly checking for
    expansion complete and was almost always returning complete
    whether it was or not.
    

Problem conclusion

  • The adminstrative console code was corrected to wait for the
    isAppReady to complete before returing application expansion
    status.   The command completing does not mean that the
    expansion completes.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.14, 9.0.0.7, .  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

    PI91760

  • 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-12-20

  • Closed date

    2018-01-17

  • Last modified date

    2018-01-17

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 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:
18 October 2021