IBM Support

PM23567: APPLICATION FAILS TO MAP OR DEPLOY, WHEN THE APPLICATION SERVER IS CREATED USING A CLUSTER TEMPLATE.

Fixes are available

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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

  • Application deployment fails when the application server is
    created with a cluster template.
    
    You will see the following exception in the FFDC logs and in
    the administrative console.
    
    ADMA5033E: The target server Server2 specified for
    CacheMonitor.war+WEB-INF/web.xml is a part of cluster
    TestCluster, but cluster TestCluster is not specified in the
    list of targets.
    
    ADMA5033E: The target server Server2 specified for
    CacheMonitor.war+WEB-INF/web.xml is a part of cluster
    TestCluster, but cluster TestCluster is not specified in the
    list of targets.
    
    Recreation Steps :
    
    - Create a cluster with one or more cluster members.
    - Create a new server template called Testtemplate and choose
    one of the cluster member.
    - Create a new Application Server with TestTemplate.
    - Deploy an application and map the application to the newly
    created server.
    

Local fix

  • Do not create an application server with cluster member
    template.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7 and V6.1                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application fails to deploy on an       *
    *                      application server created using a      *
    *                      cluster template                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an application server is created using a cluster template,
    an application deployment on such a server fails with error
    ADMA5033E (see an example below) because the server still
    retains the cluster name.
    
    ADMA5033E: The target server Server2 specified for
    CacheMonitor.war+WEB-INF/web.xml is a part of cluster
    TestCluster, but cluster TestCluster is not specified in the
    list of targets.
    

Problem conclusion

  • To prevent an application deployment failure on an application
    server created using a cluster template, we now remove the
    cluster name from such a server.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.39 and 7.0.0.17  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

    PM23567

  • 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

    2010-09-30

  • Closed date

    2011-02-07

  • Last modified date

    2011-02-07

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM23567

Modified date: 07 February 2011