IBM Support

PM12368: V7 MIGRATION - THE DEPLOYMENT.XML APPENDS A PARENT_FIRST CLASSLOADER MODE WHEN MIGRATING FROM V6.1 TO V7.0

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During Websphere Migration from V6.1 to V7.0, the deployment.xml
    appends a PARENT_FIRST classloader mode.
    
    
    In V6.1, the deployment.xml has the WAR module defined with
    PARENT_LAST classloading as such:
    
    <classloader xmi:id="Classloader_1259481640046"
    mode="PARENT_LAST"/>
    -
    <modules xmi:type="appdeployment:WebModuleDeployment"
    xmi:id="WebModuleDeployment_1259481640046"
    startingWeight="10000"
    uri="WASCHKWeb.war" classloaderMode="PARENT_LAST">
    <targetMappings xmi:id="DeploymentTargetMapping_1260437203396"
    target="ClusteredTarget_1260437203395"/>
    <classloader xmi:id="Classloader_1260437203395"/>
    </modules>
    
    However, when this WAS V6.1 was migrated to WAS V7.0, the
    deployment.xml got appended with a PARENT_FIRST
    classloader mode entry as such:
    
    <classloader xmi:id="Classloader_1268146736246"
    mode="PARENT_LAST"/>
    -
    <modules xmi:type="appdeployment:WebModuleDeployment"
    xmi:id="WebModuleDeployment_1268146736246"
    startingWeight="10000"
    uri="WASCHKWeb.war" classloaderMode="PARENT_LAST">
    <targetMappings xmi:id="DeploymentTargetMapping_1268146736246"
    enable="true" target="ClusteredTarget_1268146736245"/>
    <classloader xmi:id="Classloader_1268146736247"
    mode="PARENT_FIRST"/>
    </modules>
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server 7.0 WASPostUpgrade command who are   *
    *                  migrating from a previous release which     *
    *                  has deployed applications that contain      *
    *                  a PARENT_LAST classloader mode outside of   *
    *                  the modules definition.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: After migration a PARENT_FIRST          *
    *                      classloader mode is appended to the     *
    *                      modules definition.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During WASPostUpgrade, the default value is added to the
    modules definition for the classloader mode attribute.
    

Problem conclusion

  • The code has been corrected to only migrate the classloader
    mode attribute in the modules definition if it was specified in
    the previous release.
    
    APAR PM12368 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.13 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM12368

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-15

  • Closed date

    2010-04-27

  • Last modified date

    2010-11-02

  • 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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK61114

       UP10/10/21 P F010

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM12368

Modified date: 02 November 2010