Distinguishing Between Base and Extended Object Request Broker for versions 4.0 and 5.0
 Technote (troubleshooting)
 
Problem(Abstract)
Object Request Broker (ORB) problems are classified as either Base ORB or ORB Extensions and are handled by two different L3 or development teams: WL3ORB,103 (orb extensions) or JAVA,244 (base orb). In many cases, ORB problems manifest with a CORBA exception being thrown, and a stack trace generated.

Based on the upper level method in the stack in which the exception is thrown, you will be able to determine which ORB team should investigate, based on the full code path of the method(s). It can be confusing, since many ORB classes which were supported by the ORB Extension team in version 4.0 switched to the jurisdiction of the Base ORB team in version 5.0. But this small outline should clear up the issue. (Please note: This list is not completely extensive, but gives the more common classes in which ORB problems occur.)
 
Cause
To Be Determined...
 
Resolving the problem
WebSphere Application Server V4.0
Base ORB:
  • com.ibm.rmi
  • com.ibm.org.omg.CORBA

ORB Extensions:
  • com.ibm.CORBA.iiop
  • com.ibm.CORBA.services


WebSphere Application Server V5.0
Base ORB:
  • com.ibm.rmi
  • com.ibm.CORBA.iiop
  • com.ibm.CORBA.transport
  • org.omg.CosNaming
  • org.omg.IOP
  • org.omg.PortableInterceptor

ORB Extensions:
  • com.ibm.ws.orbimpl
  • com.ibm.ws.orb
  • com.ibm.ws.security.orbssl
  • com.ibm.CORBA.services
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Object Request Broker (ORB)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1188189
IBM Group: Software Group
Modified date: Apr 30, 2006