PK29665: SERVERS WITH STRUTS AND FRAME WORK APPLICATIONS HANG IN A DEADLOCK DURING THE SERVER INITIALIZATION

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The customer was running the application which started some
processing during WebSphere initialization, and the
initialization never completed. A deadlock occurred
 because two threads (TCB 7f9588, the main thread, and TCB
7cbe88, the WebContainer thread) were waiting on each other.
.
- ANALYZE RESOURCE
  Resource NAME=Mutex Object ADDR=27B4E160
    held by jobname BBWG41AS ASID0178 TCB=007F9588
    required by jobname BBWG41AS ASID0178 TCB=007CBE88
- Traceback (java stack for t=7f9588
Thread:   0x7f9588  ExecEnv: 0x23939ad8  Thread name:
P=2042:O=0:CT
at java/lang/Object.wait(Native Method)
at java/lang/Thread.join(Thread.java:959)
at java/lang/Thread.join(Thread.java:1012)
at com/ibm/ws/webcontainer/WebContainer.addWebApplication(WebCon
...
- Traceback (java stack for t=7cbe88)
Thread:   0x7cbe88  ExecEnv: 0x239d65d0  Thread name: Thread-17
at com/ibm/som/corba/rt/StubServices.callMethodE(Native Method)
at
com/ibm/som/corba/rt/_PseudoOrbStub.BOA_init(_PseudoOrbStub.java
:317)
at com/ibm/ws390/orb/ORB.set_parameters(ORB.java:202)
at org/omg/CORBA/ORB.init(ORB.java:397)
at jp/co/toyota/pzd1004/CIZD1119.getORB(CIZD1119.java)
...
.
This problem occurred only when the customers ran Struts and
Frame Work applications in which the user method initialized
ORB to communicate the Frame Work Servers during server
initialization.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: WebSphere Application Server Servant    *
*                      initialization hangs when loading       *
*                      Web Applications.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Server Servant initialization hangs
when attempting to load a Web Application.  The thread that
performs the Web Application loading becomes deadlocked with
the main thread performing server initialization.

This occurs when the Web Application performs an ORB.init
during the Web Application initialization code.

An analysis of the two threads in question at the time of the
deadlock will show the following java stacks:

Main Thread:
 at java/lang/Object.wait(Native Method)
 at java/lang/Thread.join(Thread.java:959)
 at java/lang/Thread.join(Thread.java:1012)
 at com/ibm/ws/webcontainer/WebContainer.addWebApplication(...)
 at com/ibm/ws/runtime/component/WebContainerImpl.install(W...)
 at com/ibm/ws/runtime/component/WebContainerImpl.start(Web...)
 at com/ibm/ws/runtime/component/ApplicationMgrImpl.start(A...)
 at com/ibm/ws/runtime/component/DeployedApplicationImpl.fi...
 at com/ibm/ws/runtime/component/DeployedModuleImpl.start(D...)
 at com/ibm/ws/runtime/component/DeployedApplicationImpl.st...
 at com/ibm/ws/runtime/component/ApplicationMgrImpl.startAp...
 at com/ibm/ws/runtime/component/ApplicationMgrImpl.start(A...)
 at com/ibm/ws/runtime/component/ContainerImpl.startCompone...
 at com/ibm/ws/runtime/component/ContainerImpl.start(Contai...)
 at com/ibm/ws/runtime/component/ApplicationServerImpl.star...
 at com/ibm/ws/runtime/component/ContainerImpl.startCompone...
 at com/ibm/ws/runtime/component/ContainerImpl.start(Contai...)
 at com/ibm/ws/runtime/component/ServerImpl.start(ServerImp...)
 at com/ibm/ws/runtime/WsServer.start(WsServer.java:145)
 at com/ibm/ws/runtime/WsServer.main(WsServer.java:243)
 at com/ibm/ws390/orb/CommonBridge.WsServerStartup(CommonBr...)
 at com/ibm/ws390/orb/ServerRegionBridge.initCSI(ServerRegi...)
 at com/ibm/ws390/orb/ORBEJSBridge.initCSI(ORBEJSBridge.jav...)

Web Application Loading Thread:
 at com/ibm/som/corba/rt/StubServices.callMethodE(Native Me...)
 at com/ibm/som/corba/rt/_PseudoOrbStub.BOA_init(_PseudoOrb...)
 at com/ibm/ws390/orb/ORB.set_parameters(ORB.java:202)
 at org/omg/CORBA/ORB.init(ORB.java:397)
 at (...Web Application code that performs ORB.init...)
 at com/ibm/ws/webcontainer/srt/WebGroup.notifyServletConte...
 at com/ibm/ws/webcontainer/srt/WebGroup.init(WebGroup.java...)
 at com/ibm/ws/webcontainer/WebContainer.addWebApplication1...
 at com/ibm/ws/webcontainer/WebContainer.run(WebContainer.j...)
 at java/lang/Thread.run(Thread.java:513)
Problem conclusion
The code under ORB.init was modified to avoid such a deadlock
from occuring.

APAR PK29665 is associated with SERVICE LEVEL W502042 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK29665
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2006-08-09
Closed date 2006-09-05
Last modified date 2006-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK29674 PK29675 PK29676

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK17760    UP06/09/08 P F609

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK29665.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK29665
IBM Group: Software Group
Modified date: Oct 3, 2006