Fix (APAR): PK74639 Status: Fix Release: 6.1.0.21 Operating System: AIX,HP-UX,i5/OS,IBM i,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: 543984 Byte size of APAR: 16345 Date: 2008-12-12 Abstract: Restoring from a repository checkpoint containing applications produces the following exception: java.lang.NullPointerException: DMA7000W: An unexpected exception occurred during o Description/symptom of problem: PK74639 resolves the following problem: ERROR DESCRIPTION:? NullPointerException in systemout during fileRepository update. LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server V6.1 PROBLEM DESCRIPTION: Restoring from a repository checkpoint containing applications produces the following exception: java.lang.NullPointerException: DMA7000W: An unexpected exception occurred during onChangeStart processing. RECOMMENDATION: None During a repository checkpoint restore in a WebSphere Extended Deployment environment, a NullPointerException is thrown. This exception only happens if the repository checkpoint includes an application in the checkpoint. The NullPointerException is logged in the SystemOut.log file of Websphere Application server. Exception Log in SystemOut.log: AppBinaryProc W ADMA7000W: An unexpected exception occurred during onChangeStart processing: java.lang.NullPointerException at com.ibm.ws.management.application.sync.AppDataMgr.addAppDocument (AppDataMgr.java:257) at com.ibm.ws.management.application.sync.AppBinaryProcessor$Change Table.handleAppDocument(AppBinaryProcessor.java:1140) at com.ibm.ws.management.application.sync.AppBinaryProcessor._onCha ngeStart(AppBinaryProcessor.java:365) at com.ibm.ws.management.application.sync.AppBinaryProcessor.access $300(AppBinaryProcessor.java:129) at com.ibm.ws.management.application.sync.AppBinaryProcessor$1.run( AppBinaryProcessor.java:305) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon troller.java:118) at com.ibm.ws.management.application.sync.AppBinaryProcessor.onChan geStart(AppBinaryProcessor.java:292) at com.ibm.ws.management.repository.FileRepository.preNotify(FileRe pository.java:1726) at com.ibm.ws.management.repository.FileRepository.update(FileRepos itory.java:1283) at com.ibm.ws.xd.admin.checkpoint.CheckpointBuilder.restoreDocument s(CheckpointBuilder.java:627) at com.ibm.ws.xd.admin.checkpoint.CheckpointBuilder.restoreCheckpoi nt(CheckpointBuilder.java:287) at com.ibm.ws.xd.admin.checkpoint.ExtendedConfigRepository.restoreC heckpoint(ExtendedConfigRepository.java:277) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265) at javax.management.modelmbean.RequiredModelMBean.invokeMethod(Requ iredModelMBean.java:1089) at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredMo delMBean.java:971) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDa taImpl.java:231) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:23 8) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Def aultMBeanServerInterceptor.java:833) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.jav a:802) at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja va:1081) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon troller.java:118) at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.j ava:974) at com.ibm.ws.console.repositorycheckpoint.action.RepositoryCheckpo intCollectionAction.execute(RepositoryCheckpointCollectionAction .java:312) at org.apache.struts.action.RequestProcessor.processActionPerform(R equestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestProcess or.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.jav a:1486) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java :528) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1074) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr apper.java:1009) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp FilterChain.java:118) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAp pFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA ppFilterManager.java:771) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA ppFilterManager.java:679) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser vletWrapper.java:539) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(S ervletWrapper.java:478) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(W ebAppRequestDispatcher.java:321) at org.apache.struts.action.RequestProcessor.doForward(RequestProce ssor.java:1070) at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesReq uestProcessor.java:273) at org.apache.struts.action.RequestProcessor.processForwardConfig(R equestProcessor.java:455) at org.apache.struts.tiles.TilesRequestProcessor.processForwardConf ig(TilesRequestProcessor.java:319) at com.ibm.isclite.container.controller.InformationController.proce ssForwardConfig(InformationController.java:206) PROBLEM CONCLUSION:? Code has been changed to allow a modified document which is supported by WebSphere Extended Deployment or Virtual Enterprise to be treated as an added document. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23. 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.1 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) _X_ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes _X_ 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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.ibm.com/support/docview.wss?rs=180&uid=swg21205400 Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension. 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into 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 and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. 8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination. 9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed. |.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both | |6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X | |6.1.0.x-WS-WAS-IFPK12345C | X | | | | |6.1.0.x-WS-WAS-IFPK12345C 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 (PKxxxxx.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: