PK41308: MIGRATION OF DEPLOYMENT MANAGER FAILS WITH NULLPOINTEREXCEPTION WHEN THERE ARE NO TARGETS ON APPLICATION TARGET MAPPINGS. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The following exception was seen during the migration of the Deployment Manager server java.lang.NullPointerException com.ibm.ws.migration.utility.UpgradeException: java.lang.NullPointerException .at com.ibm.ws.migration.postupgrade.Restore.<init> (Restore.java:249) .at com.ibm.ws.migration.postupgrade.WASPostUpgrade.restore (WASPostUpgrade.java:231) Caused by: java.lang.NullPointerException .at com.ibm.ws.migration.postupgrade.common.DeploymentConfig. arePrimaryKeysEqual(DeploymentConfig.java:231) This is caused by the fact there were applications deployed on the server being migrated that contained target mappings with null targets. An example of a target mapping with a null target from the deployment.xml file for the application is <targetMappings xmi:id="DeploymentTargetMapping_1152800221429" enable="true"/> One with a target would look like <targetMappings xmi:id="DeploymentTargetMapping_1152800221432" enable="true" target="ClusteredTarget_1152800221430"/> This apar will change the migration code so that even when there are no targets in the targetMapping, the migration will continue.Local fix Remove all targetMappings for the applications that do not have targets for the source server (the one being migrated) This can be done by replacing the deployment.xml files that are incorrect with the fixed version. Please contact level 2 for the fixed version of the xml. Then re-run the failing migration job.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.1 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: Customers migrating to version 6.1 * * may see the WASPostUpgrade step fail * * when updating applications. The * * customer will see a * * NullPointerException in the processing * * of DeploymentConfig. * **************************************************************** * RECOMMENDATION: * **************************************************************** The deployment.xml information in an EAR file can be created in an IDE, such as RAD or eclipse, and contain invalid deployment pointers. Application install ignores these invalid entries, but WebSphere migration terminates, so that the customers environment is not improperly configured during the migration step.Problem conclusion This APAR will correct the invalid deployment target information, and correctly install the application. Customers who encounter the problem should apply a fix pack that contains this APAR and rerun the PostUpgrade step of migration. APAR PK41308 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.9 of WebSphere Application Server V6.1 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PK41308.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 610
Software edition:
Reference #: PK41308
IBM Group: Software Group
Modified date: Jun 22, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.