Fix (APAR): PK81028 Status: Fix Release: 7.0.0.1,7.0.03 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: PK81028 Byte size of APAR: 10762 Date: 2009-04-04 Abstract: Application Session was removed from replication when one of it's HTTP sessions was removed Description/symptom of problem: PK81028 resolves the following problem: ERROR DESCRIPTION: NullpointerException in TWSS code caused by Session Initiation Protocol (SIP) container due to DRS_SASAttrMg is null Details: The following tests are conductions in a WebSphere Application Stever V7.0.0.1 environment. A 2 node cluster [Clust_App1 and Clust_App2]. With the node [Clust_App1] that has successfully processed the web service operation "getUserPresence" the traces show this as the output: [2/4/09 16:04:02:200 GMT+05:30] 00000036 DRS_SASAttrMg > DRS_SASAttrMgr get ENTRY Id = Clust.App1.1233741992796.0_1 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@ 58e058e com.ibm.soa.parlayx21.presence.impl.PermissionTable [2/4/09 16:04:02:200 GMT+05:30] 00000036 StandAloneSAS > StandAloneSASAttrRepoMgr get ENTRY Id = Clust.App1.1233741992796.0_1 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@ 58e058e com.ibm.soa.parlayx21.presence.impl.PermissionTable [2/4/09 16:04:02:200 GMT+05:30] 00000036 StandAloneSAS < StandAloneSASAttrRepoMgr get RETURN 2 [2/4/09 16:04:02:200 GMT+05:30] 00000036 DRS_SASAttrMg 3 DRS_SASAttrMgr get found something:class com.ibm.soa.parlayx21.presence.impl.PermissionTable@1433687412;e ntries={ } Referring to the logs for the second node Clust_App2, the logs show the following: [2/4/09 16:38:05:058 GMT+05:30] 00000040 DRS_SASAttrMg > DRS_SASAttrMgr get ENTRY Id = Clust.App2.1233745025623.0_2 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@ 2f242f24 com.ibm.soa.parlayx21.presence.impl.PermissionTable [2/4/09 16:38:05:058 GMT+05:30] 00000040 StandAloneSAS > StandAloneSASAttrRepoMgr get ENTRY Id = Clust.App2.1233745025623.0_2 Info = com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl@ 2f242f24 com.ibm.soa.parlayx21.presence.impl.PermissionTable [2/4/09 16:38:05:058 GMT+05:30] 00000040 StandAloneSAS < StandAloneSASAttrRepoMgr get RETURN nothing [2/4/09 16:38:05:058 GMT+05:30] 00000040 DRS_SASAttrMg 3 DRS_SASAttrMgr get found something:null Here is when we see the NullPointerException thrown. Ideally when the application makes a call for the required web service operation, the DRS_SASAttrMg should be returning a value for the PermissionTable which in the 2nd node is null. From the analysis this is happening at the SIP container end. The web service impl is a SIP-based service. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: All users of WebSphere Application Server V7.0 Session Initiation Protocol (SIP) container PROBLEM DESCRIPTION: Application Session was removed from replication when one of it's HTTP sessions was removed RECOMMENDATION: None If an HTTP session was invalidated on a converged SIP-HTTP application, and later a server in the cluster fails and a failover occurs, the Application Session that owned that HTTP session might not be available on the backup server. PROBLEM CONCLUSION: Only the HTTP session will be removed from the replication backup and not the owning Application Session The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.5. 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 7.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) __ Edge Components _X_ Developer Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 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 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) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the 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. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) 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: