IBM Support

PI63963: Rollout of an application edition may fail with error WPVR0011E due to condition WPVR0041W

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The customer observed the following behavior.
    
    1. edition 01 is running on dynamic cluster members.
    2. base edition is installed and uninstalled.
    3. rollout from 01 to 02 fails (WPVR0011E) due to the
    unexpected WPVR0041W.
    
    In this customer's case, the trigger of the issue is the step
    2.
    

Local fix

  • Skip the trigger operation
    
    or
    
    By restarting the cluster members between the step 2 and 3, we
    can run the rollout successfully.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Intelligent Management               *
    ****************************************************************
    * PROBLEM DESCRIPTION: The rollout of an application edition   *
    *                      may fail with error WPVR0011E due to    *
    *                      condition WPVR0041W.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Given an application edition in service (that is, the active
    edition,) when an administrator uninstalls another edition of
    the same application -- for example, uninstalls the base
    edition -- then the application server (cluster member) will
    unexpectedly deactivate the Application MBean for the active
    edition rather than the J2EEApplication MBean of the
    uninstalled edition.  Subsequently, when the administrator
    rolls out another edition of the application, the Edition
    Manager considers the active edition to be stopped
    (WPVR0041W,) due to the lack of an Application MBean, and
    attempts to start the new, active application edition on the
    target application server (cluster member.)  The new
    application edition fails to start, however, because the
    previous active edition is still in service, and ultimately,
    the rollout fails with error WPVR0011E.
    The root cause of this problem is that, when the administrator
    uninstalls another edition of the active application, the
    target Application Server (cluster member) unexpectedly
    deactivates the Application MBean for the active edition in
    service rather than the J2EEApplication MBean for the
    uninstalled edition.
    

Problem conclusion

  • Apply APAR PI63963 to ensure the Application Server
    (cluster member) deactives the corresponding J2EEApplication
    MBean when uninstalling an application edition.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11 and 9.0.0.1.  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

    PI63963

  • 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

    2016-06-09

  • Closed date

    2016-06-23

  • Last modified date

    2016-06-23

  • 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:
15 October 2021