IBM Support

PM35734: ADMINAPPLICATION.STARTAPPLICATIONONSINGLESERVER CANNOT OPERATE ON SERVER WITH SAME NAME.

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem :
    
    There are servers with same name on different nodes ( node
    name is different).
    An application is mapped to these two servers.
    In the first node, the application starts by
    AdminApplication.startApplicationOnSingleServer.
    However, in the 2nd node, if the application is started by
    AdminApplication.startApplicationOnSingleServer, it will produce
    the following error:
    ---
    Exception: exceptions.AttributeError WASL6043E: The Application:
    app-name MBean is running.
    WASX7015E: Exception running command: "AdminApplication.
    startApplicationOnAllDeployedTargets
    
    
    If the names of the application server on two nodes differ,
    there is no problem.
    It seems AdminApplication.startApplicationOnSingleServer cannot
    see the Node-name of WebSphere Application Server.
    

Local fix

  • When server name is same on different nodes, then instead of
    AdminApplication.startApplicationOnSingleServer  use following
    command to stop server :
    
    wsadmin>appManager =
    AdminControl.queryNames('cell=CELLANME,node=NODENAME,typ
    e=ApplicationManager,process=SERVERNAME,*')
    wsadmin>AdminControl.invoke(appManager, 'startApplication',
    'APPNAME')
    
    NOTE: Please replace correct values for CELLNAME, NODENAME
    ,SERVERNAME and APPNAME as per enviornment.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The startApplicationOnSingleServer      *
    *                      script library procedure on             *
    *                      AdminApplication failed when starting   *
    *                      applications on different nodes that    *
    *                      have the same server names              *
    *                      configured.  The script works fine      *
    *                      if the name of the application          *
    *                      servers on the two nodes are            *
    *                      different.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The AdminApplication startApplicationOnSingleServer script
    procedure failed when there are servers on different nodes
    with the same server names.  The application started
    successfully on the first node using the script procedure, but
    it failed to start the application on the second node with the
    following error:
    Execption: exception: AttributeError:
    WASL6043E: The application app-name MBean is running.
    WASX7015E: Exception running command:
    "AdminApplication.startApplicationOnSingleServer.
    

Problem conclusion

  • This is a bug in the AdminApplication script library.  The
    startApplicationOnSingleServer script procedure has been
    changed to query the Application MBean on a specific server
    process instead of querying it on an entire cell before starts
    an application. Now it works on nodes containing application
    servers with same name.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19.  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

    PM35734

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-28

  • Closed date

    2011-05-03

  • Last modified date

    2013-04-22

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM35734

Modified date: 22 April 2013