PK00588: JNDI PUBLISHING FROM CICS TO WAS FAILS WITH ASSERTIVE IDENTITY ENABLED.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
COS Naming fails with Asserted Identity enabled. JNDI Publishing
from CICS to WAS fails.
.
DFHII1013 E 12/21/2004 11:00:30 ADCICT01 Failure
com.ibm.cics.domains.DomainException: Class: Dfhrzsoj, function:
CREATE, response: EXCEPTION, reason: SERVICE_NOT_AVAILABLE
establishing connection to host smse5add.arag.de port 126.
DFHII1013 E 12/21/2004 11:00:30 ADCICT01 Failure
com.ibm.cics.domains.DomainException: Class: Dfhrzsoj, function:
CREATE, response: EXCEPTION, reason: SERVICE_NOT_AVAILABLE
establishing connection to host smse5add.arag.de port 126.
"NMSV0610I: A NamingException is being thrown from a
implementation: com.ibm.ejs.ns.jndi.CNContextImplᄄContext
lookupᄄContext name: ᄄTarget name:
cell/nodes/F/servers/IVTᄄOther
data: ᄄException stack trace: javax.naming.NamingException:
Error
during resolve.  Root exception is org.omg.CORBA.TRANSIENT:
com.ibm.cics.iiop.transport.CICSTransport.getRequestStream():
Class:
Dfhrzsoj, function: CREATE, response: EXCEPTION, reason:
SERVICE_NOT_AVAILABLE  vmcid: 0x4942c000  minor code: 1
completed: Noᄄᄄat
com.ibm.cics.iiop.transport.CICSTransport.handleDomainResponse(C
Dfhrzsoj, function: CREATE, response: EXCEPTION, reason:
SERVICE_NOT_AVAILABLE  vmcid: 0x4942c000  minor code: 1
completed: Noᄄᄄat
com.ibm.cics.iiop.transport.CICSTransport.handleDomainResponse(C
ICSTrans
port.java:918)ᄄ
at
com.ibm.cics.iiop.transport.CICSTransport.getRequestStream(CICST
ransport
.java:1246)ᄄ
at
com.ibm.cics.iiop.transport.CICSTransport.getConnection(CICSTran
sport.ja
va:374)ᄄ
at
com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81)ᄄ
at
com.ibm.rmi.iiop.ClientRequestImpl.reInvoke(ClientRequestImpl.ja
va:375)ᄄ
at
com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:676)
ᄄ
at
com.ibm.CORBA.iiop.ClientDelegate.invoke(ClientDelegate.java:114
8)ᄄ
at com.ibm.rmi.corba.ClientDeleg
DFHII1016 E 12/21/2004 11:00:31 ADCICT01 Failure obtaining JNDI
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Interoperability from CICS to a         *
*                      WebSphere Application server using      *
*                      asserted identity fails with CICS       *
*                      message : ADCICT01 Failure              *
*                      com.ibm.cics.domains.DomainException:   *
*                      Class: Dfhrzsoj, function:              *
*                      CREATE, response: EXCEPTION, reason:    *
*                      SERVICE_NOT_AVAILABLE establishing      *
*                      connection to host <host> port 126.     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere was configured with zSAS identity assertion enabled.
A CICS server attempted to communicate with WebSphere but failed
with a series of CICS messages.

DFHII1013 E 12/21/2004 11:00:30 ADCICT01 Failure
com.ibm.cics.domains.DomainException: Class: Dfhrzsoj, function:
CREATE, response: EXCEPTION, reason: SERVICE_NOT_AVAILABLE
establishing connection to host smse5add.arag.de port 126.

DFHII1013 E 12/21/2004 11:00:31 ADCICT01 Failure
com.ibm.cics.domains.DomainException: Class: Dfhrzsoj, function:
CREATE, response: EXCEPTION, reason: SERVICE_NOT_AVAILABLE
establishing connection to host smse5add.arag.de port 126.

DFHEJ0601 W 12/21/2004 11:00:31 ADCICT01 jndiNamingException
"NMSV0610I: A NamingException is being thrown from a
javax.naming.Context implementation. Details follow: Context
implementation: com.ibm.ejs.ns.jndi.CNContextImpl Context method
lookup Context name:  Target name: cell/nodes/F/servers/IVT Othe
data:  Exception stack trace: javax.naming.NamingException: Erro
during resolve.  Root exception is org.omg.CORBA.TRANSIENT:
com.ibm.cics.iiop.transport.CICSTransport.getRequestStream():
Class:  Dfhrzsoj, function: CREATE, response: EXCEPTION, reason:
SERVICE_NOT_AVAILABLE  vmcid: 0x4942c000  minor code: 1
completed: No  at
com.ibm.cics.iiop.transport.CICSTransport.handleDomainResponse(
CICSTrans port.java:918)  at
com.ibm.cics.iiop.transport.CICSTransport.getRequestStream(
CICSTransport.java:1246) at
com.ibm.cics.iiop.transport.CICSTransport.getConnection(
CICSTransport.java:374) at
com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:81)
at
com.ibm.rmi.iiop.ClientRequestImpl.reInvoke(
ClientRequestImpl.java:375) at
com.ibm.rmi.corba.ClientDelegate.invoke(ClientDelegate.java:676)
at com.ibm.CORBA.iiop.ClientDelegate.invoke(
ClientDelegate.java:1148)

DFHII1016 E 12/21/2004 11:00:31 ADCICT01 Failure obtaining JNDI
context for CORBASERVER ABUS, prefix cell/nodes/F/servers/IVT at
level cell/nodes/F/servers/IVT. Exception
javax.naming.NamingException: Error during resolve  Root excepti
is org.omg.CORBA.TRANSIENT:
com.ibm.cics.iiop.transport.CICSTransport.getRequestStream(): Cl
Dfhrzsoj, function: CREATE, response:EXCEPTION, reason:
SERVICE_NOT_AVAILABLE  vmcid: 0x4942c000  minor code: 1  complet
No  was received.
DFHEJ0951 E 12/21/2004 11:00:31 ADCICT01 DCICST1 State updating
failed while loading Beans from the DJar during Resolution .
processing for DJar CACT_SecurityPrototyp_EJB.

Port 126 was not available because it was not really a port
number. The WebSphere server exported an IOR with a zSAS identit
assertion tag that did not conform to the Identity Assertion
design specification. This caused CICS to think the port was
126 because it was looking at the wrong data.
Problem conclusion
The code was updated for the server to export the correct tag
and for the client to be able to read the old incorrectly
formatted tag and the new tag.

APAR PK00588 is associated with SERVICE LEVEL W502025 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK00588
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 2005-02-03
Closed date 2005-03-08
Last modified date 2005-04-16

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:
PK01248 PK04347

Modules/Macros
BBOUBINF          

Publications Referenced

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

Applicable component levels
R500 PSY UK01263    UP05/03/14 P F503

  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: swg1PK00588.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 #: PK00588
IBM Group: Software Group
Modified date: Apr 16, 2005