Fix (APAR): JR25992 Status: Fix Release: 6.0.1.x - 6.0.2.0 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: 422020 Byte size of APAR: 13727 Date: 2007-02-22 Abstract: Null Pointer Exception (NPE) on some applications while starting server after WebSphere Integration Developer iFix04 upgrade Description/symptom of problem: JR25992 resolves the following problem: ERROR DESCRIPTION: NPEs are logged into SystemOut for some apps, while starting WPS, after iFix04 upgrade Customization E com.ibm.wbiservers.customization.runtime.component.CustomizationComponentImpl stateChanged CWSTM0008E: An error occured when attempting to process a Business Rules or Selector artifact during startup. Check the artifact to make sure it is valid XML. java.lang.NullPointerException at com.ibm.ws.management.repository.FileRepository.getFiles(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.addResourceNames(FileRepository.java(Compiled Code)) at com.ibm.ws.management.repository.FileRepository.listResourceNames(FileRepository.java:1738) at com.ibm.wbiservers.customization.runtime.component.CustomizationComponentImpl.findTimestampForApp(CustomizationComponentImpl.java:399) at com.ibm.wbiservers.customization.runtime.component.CustomizationComponentImpl.appStart(CustomizationComponentImpl.java:358) at com.ibm.wbiservers.customization.runtime.component.CustomizationComponentImpl.stateChanged(CustomizationComponentImpl.java:337) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java(Compiled Code)) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:1050) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:210) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:737) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:909) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2020) at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471) LOCAL FIX: NONE PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.1.x users WebSphere Process Server 6.0.2.0 users PROBLEM DESCRIPTION: Null Pointer Exception (NPE) on some applications while starting server after WebSphere Integration Developer iFix04 upgrade RECOMMENDATION: None The problem is with the code to access the configuration files which is not guarenteed to work and will fail in a ND environment and on fast machines where there can be a timing issue too. The problem is random in nature, not specific to any application or artifacts, and is not speciifc to any plugin changes. Using the same systems during 6.0.2.0 testing or having a different number of applications or some other differece in the system configuration/hardware will cause the timing differences. PROBLEM CONCLUSION: The fix uses code which is guarenteed to find the files correctly. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1/2 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: