PQ83657: AUTOSTARTED SERVLET-INIT METHOD CREATES AN EJB A LOCKOUT OCCURS.THREAD HANGS PTHREAD_MUTEX_LOCK BOA_INIT_LOCK WAITING IN THREAD

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Autostarted-servlet process added a new thread under which
the ServletManager is created and the load of autostart
servlets is done. In the case where a user's servlet init method
creates an EJB a lockout occurs as follows:
..
Traceback for hung thread TCB=xxxxxx
CEEOPML2    (pthread_mutex_lock)
Lock::obtainLock()
CORBA::ORB::BOA_init(int&,char**,char*)
Java_com_ibm_ws390_orb_ORBEJSBridge_createIOR
..
The IPT thread owns the BOA_init_lock and ends up waiting in
Thread.  join for the Servlet Manager thread to terminate.
The Servlet manager thread gives control to the user's servlet
init method, in the case where it wants to create an EJB it
drives the BOA_init code via createIOR which waits for the
BOA_init_lock.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: If an autostarted servlet causes the    *
*                      createIOR native method to be driven,   *
*                      a hang ensues.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If an autostarted servlet does home lookups and creates EJBs
then a hang can ensue.
The main thread will be holding a mutex and waiting for
autostarted servlet processing to complete.  Another java
thread will hang in createIOR's call to BOA_init waiting for
the mutex to become available.
Problem conclusion
The call to BOA_init can be skipped on the createIOR path in
in a servant since it is already complete.

APAR PQ83657 is associated with SERVICE LEVEL W502002 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ83657
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 2004-01-23
Closed date 2004-02-12
Last modified date 2004-03-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

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

Applicable component levels
R500 PSY UQ85128    UP04/02/20 P F402

  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: swg1PQ83657.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 #: PQ83657
IBM Group: Software Group
Modified date: Mar 3, 2004