Download
Abstract
The Session Initiation Protocol (SIP) proxy was not correctly catching all affinity lookup failures.
Download Description
PK80196 resolves the following problem:
ERROR DESCRIPTION:
When a Session Initiation Protocol (SIP) container goes into failover, the SIP proxy returns back 404 error responses to SIP requests that contain affinity to the failed server. It should be suspending these until the peer SIP container has taken over the failed servers sessions.
LOCAL FIX:
PROBLEM SUMMARY
USERS AFFECTED:
All users of IBM WebSphere Application Server V7.0
PROBLEM DESCRIPTION:
The Session Initiation Protocol (SIP) proxy was not correctly catching all affinity lookup failures.
RECOMMENDATION:
None
The SIP proxy was not correctly catching all affinity look-up failures and suspending the processing of these SIP requests until the SIP container's peer server has taken over the sessions of the failed server.
PROBLEM CONCLUSION:
The SIP proxy is now catching all affinity look-up failures and suspending the processing of these SIP requests until failover has completed. Once failover has completed the SIP proxy resumes the processing of the suspended SIP requests which are then sent to the SIP container that activated the SIP sessions of the failed SIP container.
The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.3. Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Prerequisites
Please download the UpdateInstaller below to install this fix.
Installation Instructions
Please review the readme.txt for detailed installation instructions.
Technical Support
Contact IBM Support using SR (http://www-306.ibm.com/software/support/probsub.html), visit the WebSphere Application Server Support Web site (http://www.ibm.com/software/webservers/appserv/was/support/), or contact 1-800-IBM-SERV(U.S. only).
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg24022478