Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
In a multi-homed environment when an ACK request arrives from th
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All Session Initiation Protocol (SIP) * * container users of IBM WebSphere * * Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: In a multi-homed environment when a * * request arrives from the SIP Container * * internal queue (a.k.a. a loopback * * request), the SIP Container might * * choose a wrong interface when trying * * to send a request to the destination. * **************************************************************** * RECOMMENDATION: * **************************************************************** In a multi-homed environment when a request arrives from the SIP Container internal queue (a.k.a. a loopback request), the SIP Container might choose a wrong interface when trying to send a request to the destination.
Problem conclusion
A fix was made in the SIP Container code so the IBM proprietary IBM-PO header field which was causing the issue is not added to loopback requests. The following SIP Container custom property should be applied to the server: Name: add.ibm-po.loopback.msg Value: false Log into the WebSphere administrative console. Click Application servers > <server_name> > SIP container > Custom properties Add the new custom property by clicking on New In the Name field enter: add.ibm-po.loopback.msg In the Value field enter: false Click on the OK button Restart the server The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.14 and 9.0.0.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI93796
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-14
Closed date
2018-03-17
Last modified date
2018-03-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022