PQ51685: EJB CLIENT (SERVLET) GOT SIGSEGV IN RESOLVE_INITIAL_REFERENCES -> COMM_OUTBOUND_REQUEST() -> ENCAPIIOP::ENCAPIIOP

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
EJB Client got SIGSEGV (abend0c4) in resolve_initial_references
-> InitialReferences_ORBProxy::get -> CORBA::Request::invoke()
-> ORB_Request::comm_outbound_request() -> EncapIIOP::EncapIIOP.
The client ran in servlet. Service level was at W400014.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: ABEND0C4/ABENDS0C4 occurs in            *
*                      EncapIIOP::EncapIIOP in bboceiop.cpp    *
*                      under comm_outbound_request from        *
*                      resolve_initial_references issued from  *
*                      multi-threaded Java client (e.g.        *
*                      webserver).                             *
*                                                              *
*                      Additional symptom is a CEEDUMP which   *
*                      shows an exception in method            *
*                      ORB_Request::comm_outbound)locate()     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
comm_outbound_request passes a thread level structure to the
EncapIIOP constructor.  The thread level structure is created
as part of ORB_init processing.  ORB_init must be called for
each thread in the process. In some cases the client application
is not aware of a difference is dispatch threads between methods
and may not do the required ORB_init call.  In these cases the
underlying Java/C++ ORB implementation should do the required
ORB_init processing on the applications behalf to ensure thread
level structures are properly created.
Problem conclusion
Support has been changed for ORB methods implemented in the
Shasta layer to call ORB_init prior to using the ORB pointer
obtained from an ORB_init done previously in the process, but
not necessarily on this thread.

APAR PQ51685 is associated with SERVICE LEVEL W400032 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ51685
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-08-22
Closed date 2001-09-13
Last modified date 2001-10-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
UQ57634

Modules/Macros
BBOLPOI BBOUBINF        

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ57634    UP01/09/26 P F109

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ51685
IBM Group: Software Group
Modified date: Oct 3, 2001