Fix (APAR): PK48446 Status: Fix Release: 6.0.2.19 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK48446 Byte size of APAR: 18000 Date: 2007-07-31 Abstract: A null pointer exception is thrown from cscope code when attempting to perform recovery on a server that is started in RecoveryOnly mode. Description/symptom of problem: PK48446 resolves the following problem: ERROR DESCRIPTION: Nullpointer exception in cscope code when starting server in recovery mode after a crash. Here is an example of the exception when this takes place [7/3/07 18:45:48:985 GMT+01:00] 0000000a RecoveryManag E CSCP0014E: During Compensation Scope recovery a recreation attempt failed. The cause of the failure was java.lang.NullPointerException at com.ibm.ws.cscope.RecoveryManager.processRecoveredData(RecoveryM anager.j ava:538) at com.ibm.ws.cscope.RecoveryManager.setServerStatus(RecoveryManage r.java:4 05) at com.ibm.ws.cscope.CScopeRecoveryAgent.setServerStatus(CScopeReco veryAgen t.java:295) at com.ibm.ws.cscope.CScopeComponentImpl.propertyChange(CScopeCompo nentImpl .java:586) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChan geSuppor t.java:330) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChan geSuppor t.java:257) at com.ibm.ws.runtime.component.ComponentImpl.setState(ComponentImp l.java:4 01) at com.ibm.ws.runtime.component.ComponentImpl.setStartState(Compone ntImpl.j ava:421) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:41 5) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl .java:18 7) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod Accessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:534 LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: All IBM WebSphere Application Server versions 6.0.2 and 6.1 users of the Compensation Service. PROBLEM DESCRIPTION: A null pointer exception is thrown from cscope code when attempting to perform recovery on a server that is started in RecoveryOnly mode. RECOMMENDATION: None As part of cscope recovery, the recovery service attempts to drive all recovered compensations to completion after recording transaction outcomes in the cscopes that require recovery. When a server is started in RecoveryOnly mode, only those services required by the application server for recovery processing are started. This precludes starting the Activity Service, and any applications. The null pointer exception was thrown because the recovering cscope was attempting to reference the non-started Activity Service. Here is an example of the exception when this takes place [7/3/07 18:45:48:985 GMT+01:00] 0000000a RecoveryManag E CSCP0014E: During Compensation Scope recovery a recreation attempt failed. The cause of the failure was java.lang. NullPointerException at com.ibm.ws.cscope.RecoveryManager.processRecoveredData (RecoveryManager.java:538) at com.ibm.ws.cscope.RecoveryManager.setServerStatus (RecoveryManager.java:405) at com.ibm.ws.cscope.CScopeRecoveryAgent.setServerStatus (CScopeRecoveryAgent.java:295) at com.ibm.ws.cscope.CScopeComponentImpl.propertyChange (CScopeComponentImpl.java:586) at java.beans.PropertyChangeSupport.firePropertyChange (PropertyChangeSupport.java:330) at java.beans.PropertyChangeSupport.firePropertyChange (PropertyChangeSupport.java:257) at com.ibm.ws.runtime.component.ComponentImpl.setState (ComponentImpl.java:401) at com.ibm.ws.runtime.component.ComponentImpl.setStartState (ComponentImpl.java:421) at com.ibm.ws.runtime.component.ServerImpl.start (ServerImpl.java:415) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer (WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:534) PROBLEM CONCLUSION: If the server is started in RecoveryOnly mode, transaction outcomes are recorded (as normal) in cscopes that require recovery, but no attempt is made to drive the outstanding compensations to completion. This prevents the recovering cscope from attempting to reference the non-existent Activity Service. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.23 and 6.1.0.13. 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: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ 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.2 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 PKxxxxx.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 (PKxxxxx.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 (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: