PQ96362: DAEMON ABNORMALLY ENDS WITH ABEND CC3 MINOR CODES C9C20009 AND C9C211C8 AND 0C4 IN ORB_REQUEST::SEND_MESSAGE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
In the Daemon job log:
BBOO0010W The function Internal_CORBA_Request::
          Associate_ORB_Request(ORB_Request *)+263 raised CORBA
          system exception CORBA::INTERNAL.  Error code is
          C9C211C8.
followed by
BBOO0111E Attempt to dispatch method get of class
          InitialReferences encountered uncaught system
exception
          CORBA::INTERNAL.
followed by
BBOO0033W Processing for signal 'SIGSEGV' (11) with  si_code=
          'SEGV_PROTECT'
indicating the 0C4.  Then
BOO0034W Terminating the current thread (2782D300 0000000A),
REASON=C9C20009.
And finally
BBOO0009E WEBSPHERE FOR Z/OS DAEMON D102 ENDED ABNORMALLY,
REASON=C9C212C4.
.
The C9C212C4 is just a WebSphere address space cancelling itself
because of the prior errors.  C9C20009 is also generic.  These
two minor codes without the other symptoms is not a match for
this problem.
.
Callback stack for the 0C4 (SIGSEGV / SEGV_PROTECT)
ORB_Request::send_message
ORB_Request::construct_and_send_message
ORB_Request::comm_outbound_response()
outbound_response
ACR_ExecutionThread::ProcessInboundRequest
ACR_ExecutionThread::RemoveAndProcessWork
ACR_ExecutionRoutine
.
The 0C4 occurs in send_message because the session object
pointer in the session handle is bad.  The response was trying
to be sent back for the C9C211C8 exception for a request on
method get and classname InitialReferences.  C9C211C8 indicates
the non-HTTP request doesn't have a NLS Service Context.  In V5,
the Daemon doesn't expect to receive any
resolve-initial-references (RIR) requests.  This apar is being
take to prevent the code in the Daemon from taking the 0C4 when
trying to send the exception for C9C211C8.
.
The callback stack for the 0C4 may also look like the following
and is another symptom of this same problem:
.
CredBucket::findBucket(CredKey*)
              2D052C78  +00000098         121  BBOSEC    W510200
SecurityManager::sendResponse(ORB_Request*)
              2CF70F50  +00000290        2237  BBOSEC    W510200
ORB_Request::comm_outbound_response()
              2C86D5D8  +00000EC6        6243  BBOBOA    W510200
outbound_response(ORB_Request*)
              2C820540  +00000024         657  BBOBOA    W510200
ACR_ExecutionThread::ProcessInboundRequest(acrwObj*,ThreadCl
de=SEGV_PROTECT                   11/10/04 8:46:28 PM
              2C826300  +000006D8        2185  BBOBOA    W510200
ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)
              2C832088  +00000686        5527  BBOBOA    W510200
ACR_ExecutionRoutine
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: An ABEND0C4/ABENDS0C4 in the Daemon in  *
*                      orb_request::send_message attempting    *
*                      to send a GIOP response containing a    *
*                      CORBA::INTERNAL exception with minor    *
*                      code C9C211C8.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The 0C4 occurs in send_message because the session object
pointer in the session handle is bad.  The response was trying
to be sent back for the C9C211C8 exception for a request on
method get and classname InitialReferences. C9C211C8 indicates
the  IIOP request doesn't have a NLS Service Context. In
WebSphere Application Server V5.0 for z/OS,  the Daemon does not
expect to receive any resolve-initial-references (RIR) requests.
Problem conclusion
Code has been modified to not process the InitialReferences::get
method in the Daemon.

APAR PQ96362 is associated with SERVICE LEVEL W502019 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ96362
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-10-27
Closed date 2004-11-19
Last modified date 2005-01-05

APAR is sysrouted FROM one or more of the following:
PQ96361

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 UQ95286    UP04/12/03 P F412

  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: swg1PQ96362.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 #: PQ96362
IBM Group: Software Group
Modified date: Jan 5, 2005