Fix (APAR): PK84684 Status: Fix Release: 7.0.0.3,7.0.0.1 Operating System: AIX,HP-UX,IBM i,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,Solaris,Windows,z/OS Supersedes Fixes: PK83245,PK81897,PK84839,PK83477,PK82137 CMVC Defect: PK84684 Byte size of APAR: 155120 Date: 2009-05-24 Abstract: If SIP session invalidate() was called while an INVITE is un-answered - a memory leak is created. Description/symptom of problem: PK84684 resolves the following problem: ERROR DESCRIPTION: Premature termination issue: Can be observed in Session Initiation Protocol (SIP) B2B UA scenarios. 1st leg sends INVITE and immediately invalidates the SIP application session. 1.The INVITE was already sent to the 2nd leg. SIP container disposed (almost) all the related objects. In order to clean the SIP stack memory, SIP Container needs to send a CANCEL request on the 2nd leg. However an error is issued (IllegalStateException) since the SIP Container already invalidated most of the needed objects. Even if the SIP Container wanted to send an immediate CANCEL , according to RFC 3261, it must wait for some response to arrive first (most likely for INVITE is a 180 Ringing response). 2.SIP container also canceled the Sip Application timer that could terminate the call gracefully. 3.When SIP container got the 180 response for such INVITE it changed that dialog from TERMINATED state to EARLY . That should be blocked in the dialog state machine Solution: Container has invalidated a session and sent INVITE but never got a response. The Session termination will be postponed until some response or until 32 seconds have passed. If in the mean time a provisional response arrives : a CANCEL will be sent to the UAS. LOCAL FIX: n/a PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server V7.0 who also use the Session Initiation Protocol (SIP) Container. PROBLEM DESCRIPTION: If SIP session invalidate() was called while an INVITE is un-answered - a memory leak is created. RECOMMENDATION: None A SIP flow problem in B2B UA scnearios may cause a memory leak. PROBLEM CONCLUSION: A new timer was created if an INVITE transaction is not yet finished (32 seconds). A CANCEL request is sent to the UAS when the INVITE transaction is complete (i.e. when provisional response arrives). 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) 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 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 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: This iFix contains several issues . Even if the siplet is not B2B UA scenario it also addresses a general CSeq replication problem when running SIP applications with HA enabled and DRS .it also fixes a problem with SIP Application expiration timer not triggered in some scenarios. Therefore it is highly recommended .