IBM Support

PI77452: AdminTask.setMaintenanceMode sets the wrong server when the node name is wrong

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • when using the following command to set maintanance mode:
    /wsadmin.sh -user <username> -password <password> -lang
    jython
    -c "AdminTask.setMaintenanceMode ('<nodename>','[-name
    <server_name> -mode <mode>]')"
    if you define the wrong node name, it will set the
    maintenance
    mode to a wrong server.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All Users of IBM WebSphere Application      *
    *                  Server Virtual Enterprise/IM Component      *
    ****************************************************************
    * PROBLEM DESCRIPTION: AdminTask.setMaintenanceMode does not   *
    *                      detect an incorrect node name           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the AdminTask.setMaintenanceMode command the user
    provides a node and server name which will get set into
    maintenance mode. If the node name is incorrect, the command
    does not report it and will instead set an arbitrary server into
    maintenance mode.
    

Problem conclusion

  • The node name and server name refer to a unique configuration
    location. Code was altered to ensure that the node name is
    correct and that the requested server exists on that node. If
    either of these items are incorrect an error message is
    displayed from wsadmin which notifies the user of failure, and
    it indicates there was a problem with setting maintenance mode
    on for that server by either reporting the incorrect node name
    or informing the user that the server does not exist on that
    node.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.12.  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

    PI77452

  • 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-03-01

  • Closed date

    2017-03-29

  • Last modified date

    2017-03-29

  • 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

[{"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