Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
If the SIP Container goes out of view, then comes back into view, the TLS connection between the SIP Proxy and the SIP Container may not be re-established.
Local fix
the customer needs to enable SIP Network Outage Detection for the SIP Proxy. This will force data over the TCP connection and quickly determine if there is a network issue. Here is a link for enabling this feature ---> http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=% 2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Ftjpx _sippxnetout.html
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Session Initiation Protocol (SIP) * * Proxy * **************************************************************** * PROBLEM DESCRIPTION: When a SIP Proxy and SIP Container * * are working properly, then the SIP * * Container is restarted, the SIP Proxy * * may not re-connect to the SIP * * Container when it restarts. * **************************************************************** * RECOMMENDATION: * **************************************************************** Sometimes, the SIP Proxy does not re-connect to the SIP Container after a SIP Container restarts.
Problem conclusion
The SIP Proxy is not managing its connections to the SIP Container properly. After a SIP Container restart, it should re-connect to the SIP Container, but in some instances it does not. The code has been fixed so this is no longer a problem. As a work-around, you should enable "SIP Network Outage Detection" from the Administrative console. This will ensure that the SIP Proxy manages the connections properly. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.29, 8.0.0.6, and 8.5.0.2. 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
PM76236
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-31
Closed date
2012-12-26
Last modified date
2012-12-26
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021