Fix (APAR): PK33212 Status: Fix Release: 6.0.2.17 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PK33212 Byte size of APAR: 32371 Date: 2007-06-21 Abstract: NullPointerException is thrown on Deployment Manager traces, during a Save operation after updating the deployment.xml of the application. Description/symptom of problem: PK33212 resolves the following problem: ERROR DESCRIPTION: NullPointer Exception thrown during onChangeStart event processing of AppSync Exception in the log file. [10/11/06 21:47:28:578 EDT] 00000045 AppBinaryProc W ADMA7000W: An unexpected exception occurred during onChangeStart processing: java.lang.NullPointerException at com.ibm.ws.management.application.sync.AppDataMgr.updateDeplData (AppData Mgr.java:321) at com.ibm.ws.management.application.sync.AppDataMgr.addAppDocument (AppData Mgr.java:178) at com.ibm.ws.management.application.sync.AppBinaryProcessor$Change Table.ha ndleAppDocument(AppBinaryProcessor.java:1051) at com.ibm.ws.management.application.sync.AppBinaryProcessor._onCha ngeStart (AppBinaryProcessor.java:298) at com.ibm.ws.management.application.sync.AppBinaryProcessor.access $300(App BinaryProcessor.java:121) at com.ibm.ws.management.application.sync.AppBinaryProcessor$1.run( AppBinaryProcessor.java:247) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon troller.java(Compiled Code)) at com.ibm.ws.management.application.sync.AppBinaryProcessor.onChan geStart(AppBinaryProcessor.java:241) at com.ibm.ws.management.repository.FileRepository.preNotify(FileRe pository.java:1641) WebSphere Application Server 6.0.2.X. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server users of version 6.0.2.x and 6.1.0.x PROBLEM DESCRIPTION: NullPointerException is thrown on Deployment Manager traces, during a Save operation after updating the deployment.xml of the application. RECOMMENDATION: None A NullPointerException is being thrown during Save operation after an application update, in a Network Deployment environment. During the Save operation after an application update, the binariesURL path will be expanded to reflect the changes to the installedApps directory, if needed. The NullPointerException is thrown while expanding the variable in the binariesURL path, if the variable is defined at the scope of the target server or its node, in a Network Deployment environment. As per our design the variable defined at a server scope or its node scope will not be visible to the Deployment Manager server. Since, during a Save operation, Deployment Manager tries to resolve the variable in the binariesURL path that is defined beyond its scope, it fails to resolve and throws the NullPointerException. The binariesURL path is valid only with regard to the Application Server Node. Because binariesURL path has no role on the Deployment Manager, the failure in resolving the variable in the binariesURL path on the Deployement Manager is of no harm. PROBLEM CONCLUSION: Since the binariesURL path has no role on the Deployment Manger, resolving the variable in it is not required. The fix skips the resolving logic if it is on the Deployment Manager. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.19 and 6.1.0.9. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: Fix applies to Editions: Release 6.0 _Y_ Application Server (Express or BASE) _Y_ Network Deployment (ND) Install Fix to: Method: _Y_ Application Server Nodes _Y_ Deployment Manager Nodes _Y_ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.7 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy 6.0.2.17-WS-WAS-IFPK33212.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (6.0.2.17-WS-WAS-IFPK33212.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (6.0.2.17-WS-WAS-IFPK33212.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: