PQ76477: V5 SERVANT REGION CAN'T BE STARTED WITH GIOP1.1

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Tried to start WebSphere for z/OS V5 server at GIOP1.1 by
defining the following in was.env:
protocol_giop_level_highest=1.1
Confirmed that the above definition was picked up the servant
region in its job log via
BBOM0001I protocol_giop_level_highest: 1.1.
Later, during initialization of the servant region, the
following exception was thrown:
javax.naming.ServiceUnavailableException: Could not obtain
initial context with the URL
"corbaloc:rir:/NameServiceServerRoot".  Root exception is
org.omg.CORBA.BAD_PARAM: Invalid GIOP version 1.2  minor code:
4F4D0009  completed: No
 at
com.ibm.ws390.orb.IIOPAddrImpl.setVersion(IIOPAddrImpl.java:161
)
 at com.ibm.ws390.orb.IIOPAddrImpl.<init>
(IIOPAddrImpl.java:104)
 at com.ibm.ws390.orb.IorURL.setupIorURL(IorURL.java:175)
 at com.ibm.ws390.orb.IorURL.<init>(IorURL.java:145)
 at com.ibm.ws390.orb.ORB.createObjectURL(ORB.java:722)
 at com.ibm.ws390.orb.ORB.createObjectURL(ORB.java:686)
 at com.ibm.ws390.orb.ORB.string_to_object(ORB.java:517)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.stringToObject(WsnInit
CtxFactory.java:1235)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnI
nitCtxFactory.java:774)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServ
er(WsnInitCtxFactory.java:689)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(Wsn
InitCtxFactory.java:590)
 at
com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInter
nal(WsnInitCtxFactory.java:481)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:10
2)
 at
com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.j
ava:408)
 at
com.ibm.ws.naming.util.WsnInitCtx.getNameParser(WsnInitCtx.java
:330)
 at
javax.naming.InitialContext.getNameParser(InitialContext.java:4
41)
 at
com.ibm.websphere.naming.JndiHelper.recursiveRebind(JndiHelper.
java:356)
 at
com.ibm.ws.runtime.component.MetaDataMgrImpl.bindMetaDataServic
e(MetaDataMgrImpl.java:289)
 at
com.ibm.ws.runtime.component.MetaDataMgrImpl.start(MetaDataMgrI
mpl.java:154)
 at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(Cont
ainerImpl.java:343)
 at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.
java:234)
 at
com.ibm.ws.runtime.component.ApplicationServerImpl.start(Applic
ationServerImpl.java:117)
 at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(Cont
ainerImpl.java:343)
 at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.
java:234)
 at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:2
09)
 at com.ibm.ws.runtime.WsServer.start(WsServer.java:145)
 at com.ibm.ws.runtime.WsServer.main(WsServer.java:245)
 at
com.ibm.ws390.orb.CommonBridge.WsServerStartup(CommonBridge.jav
a:322)
 at
com.ibm.ws390.orb.ServerRegionBridge.initCSI(ServerRegionBridge
.java:157)
 at
com.ibm.ws390.orb.ORBEJSBridge.initCSI(ORBEJSBridge.java:151)
 com.ibm.ws.runtime.WsServer com.ibm.ws.runtime.WsServer
Local fix
Ensure that protocol_giop_level_highest=1.1 is specified for all
servers including the daemon.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Over-strict parsing of IIOP versions    *
*                      in IORs resulting in                    *
*                      org.omg.CORBA.BAD_PARAM exception with  *
*                      minor code 4F4D0009.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
IOR parsing must handle higher IIOP level than supported by
the current server (since remote server may support a higher
giop level than we do, and this would be indicated by the
major/minor level included in the IIOP profile of the IOR).
Problem conclusion
Support has been modified to avoid checking against restrictive
version ceiling, and verify only that IIOP version specified in
IOR is valid.

APAR PQ76477 is associated with SERVICE LEVEL W500104 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ76477
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 2003-07-17
Closed date 2003-08-30
Last modified date 2003-10-03

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

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 UQ79825    UP03/09/10 P F309

  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: swg1PQ76477.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 #: PQ76477
IBM Group: Software Group
Modified date: Oct 3, 2003