Fixes are available
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
WebSphere Application Server Network Deployment edition 6.1.0.17 Linux operating system Customer cannot deploy new application. ---------------------------------------------------------------- -------- [6/16/09 12:22:39:767 UTC] 00000344 FailoverDataR E FailoverDataReactivator CWSCT0335E: Failed to reactivate objects after failover. [6/16/09 12:22:39:768 UTC] 00000344 FailoverDataR E FailoverDataReactivator java.lang.NullPointerException at com.ibm.ws.sip.container.servlets.SipSessionImplementation.updat ePerform anceAboutNewSession(SipSessionImplementation.java:884) at com.ibm.ws.sip.container.servlets.SipSessionImplementation.activ ate(SipS essionImplementation.java:1067) ---------------------------------------------------------------- --------
Local fix
Customer restarts entire cluster to allow deployment of application.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V6.1 * **************************************************************** * PROBLEM DESCRIPTION: Session Initiation Protocol (SIP) * * container terminated the server when * * all applications stopped. * **************************************************************** * RECOMMENDATION: * **************************************************************** After all applications were stopped, the server ignored heartbeat messages from the proxy server. After not receiving heartbeat messages the server terminated itself.
Problem conclusion
A code fix allowed heartbeat message to be processed even when all applications were stopped. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.27. 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
PK90094
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
2009-06-29
Closed date
2009-08-13
Last modified date
2009-08-13
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
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
28 December 2021