PI44159: ACTIVATION SPECS NOT STARTED IN ALL SERVERS IN A CLUSTER DURING SERVER INITIALIZATION.

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• A timing/synchronization issue has been detected resulting in
  some Activation Specs not being  started during server
  initialization.     Problem occurs sporadically and is highly
  timing sensitive.
  

Local fix

• Start/Resume Activation Specs from ISC or via scripting.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When system property                    *
  *                      com.ibm.ejs.j2c.J2CServerListener.activ *
  *                      ateEndpointsOnCRA                       *
  *                      Started = true,                         *
  *                      WebSphere Application Server for z/OS   *
  *                      intermittently fails to start           *
  *                      Activation Specs after server startup.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  WebSphere Application Server for z/OS has a timing window
  during initialization wherein a servant region will miss the
  notification that the control region has completed
  initialization. A thread in the servant region waits in the
  background for this notification forever, never starting its
  Activation Specs.
  

Problem conclusion

• The code has been updated to eliminate this timing window.
  
  APAR PI44159 is currently targeted for inclusion in Fix Packs
  8.0.0.12 and 8.5.5.8 of WebSphere Application Server for z/OS.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

Temporary fix

Comments

APAR Information

• 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 FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R850 PSY

     UP