Fix (APAR): PK31203 Status: Fix Release: 6.1.0.3 Operating System: AIX,i5/OS,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 1353210 Date: 2006-11-28 Abstract: This APAR contains a set of fixes for the SIP Servlet Container. These fixes are related to performance, high-availability, and interoperability. Description/symptom of problem: PK31203 resolves the following problem: ERROR DESCRIPTION: This APAR References SIP Container and SIP Proxy fixes affecting all platforms LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6.1 users of the SIP component. PROBLEM DESCRIPTION: This APAR contains a set of fixes for the SIP Servlet Container. These fixes are related to performance, high-availability, and interoperability. RECOMMENDATION: None Fixes the following defects: * Outbound SIP conns fail without priming system * Invite2xxRetransmitTimer is not cancelled when ACK received * IMS SVT: Heavy load sip container routes request to wrong port * Messages lost clustered configuration * Error parsing a message with body starting with a whitespace * Routing rules with no conditions returns true. * IMS#RLJC6RQ6LT - SipRouter CWSCT0017E: Mapping for nonexisting * CANCEL of INVITE * SIP Proxy drops TCP connections causing OutOfMemory * IMS SVT (RLJC6RQ6LT): SipRouter CWSCT0017E: Mapping for nonexisting * SIP replication: optimize throughput and garbage collection * White space in Accept-Language header not handled properly. * Support for RFC 3515 - REFER * zFVT: invalid chain name exceptions * Proxy stops processing TLS requests under stress * Should take transport from route header instead of default * SIP Proxy should create a new SIP connection * SIP Container should create a new SIP connection * Container delivers messages out of order * Out of Memory error during 1 day stress run * Z/OS no keepAlives flowing from siprouter to container * SIP Container: message content is logged * IMS: container.timer timeout causes exception * Need custom property to allow Sip proxy to route message * Support user affinity in the proxy (based on the To header) * New call activity ignoring DRS congestion events * Container Process is bootstrapping twice during startup * stop Server did not stop completely - process for CR stil * SIP Container remains available when no apps are running * Not handling whitespace correctly on a Content-Length header * LB Filter not sorting list of servers for hashing algorithm * Sip Sessions not being replicated * Proxy continues to send new request queising a SIP container * SIP ignores port number in Via header * Exception on load * IllegalStateException "Task already scheduled or cancelled" * Numerous exceptions occuring when running B2BUA test * Restarting SIP container in Network Deployment environment causes exceptions * SIP Container sends UDP requests to proxy that is not up. * SIP Container notifies WLM before bootstrap completes. * Problem using private UCF SPIs in SIP container code * Container blocks when making outbound TCP connection. * sips schema in Contact header if sips schema in request URI * Proxy java.lang.ExceptionInInitializerError after Failover * Change default HA algorithm * When CSeq order violated in a dialog, send "500..." * SipFactory tossing out parameters in the SIP "from" header * Container not expiring timers properly on replicated servers. * Quiescing a container results in call failures * Memory leak in SIP app on HA cluster * IMS SIP: Do not append space to Accept in SUBSCRIBE request * SIP Container not handling new line in Content-Type header * RequestDispatcher NullPointerException * Random SIP Timer Exception * Starting Server after quiece results in timeouts and retransmissions * SIP PMI Counters incorrect after quiesce * Queue Size PMI counter exceeding established boundary * Quiescing collocated SIP containers causes failures * SystemOut never reports when queue is no longer overload * Remove FFDC print when calling getDesiredWeight * Recovered proxy can't find containers * NullPointerException when retransmission of ACK received * RIR locate of SipLogicalServerRegistry fails * Proxy continues to send new request queising a SIP container * sips schema in Contact header if sips schema in request duplicate PROBLEM CONCLUSION: The fix for this APAR is currently targeted for inclusion in fixpack 6.1.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: 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: