Fixes are available
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
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
As a server is starting and WOLA requests arrive while the servant is initializing, the control region threads can all be busy handing the WOLA requests and there aren't resources available to finish bringing up the Servant. So the servant fails to reach e-business. A dump of the servant shows a startup thread hung: name: server.startup : 0 Java stack frames: com/ibm/ws390/orb/ClientDelegate.invokeRequestCFW com/ibm/ws390/orb/ClientDelegate.commonInvoke com/ibm/ws390/orb/ClientDelegate.invoke org/omg/CORBA/portable/ObjectImpl._invoke com/ibm/WsnOptimizedNaming/_NamingContextStub.get_compatibility_ level() com/ibm/ws/naming/util/CommonHelpers$5.run() A dump of the control region shows the threads are handling ola calls
Local fix
delay sending inbound WOLA requests until the server is fully up
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.0 and V8.5 Optimized Local * * Adapters * **************************************************************** * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS * * Servant region hangs on startup when * * sending a large number requests to * * WebSphere Optimized Local Adapter * * While WebSphere is initializing. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server running WebSphere Optimized Local Adapters (WOLA) can enter a deadlocked condition if a large number of WOLA requests are sent to the server before the server has completed initialization.
Problem conclusion
Updated the JNDI lookup by WOLA to execute on a thread in the default thread pool instead of on a WebSphere worker thread preventing the deadlocked condition from happening. APAR PI38626 is currently targeted for inclusion in Fix Packs 8.0.0.12 and 8.5.5.7 WebSphere Application Server. 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 number
PI38626
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-08
Closed date
2015-08-10
Last modified date
2015-08-10
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
Document Information
Modified date:
28 April 2022