|
Problem |
ORB problems are classified as either Base ORB or ORB
Extensions and are handled by two different L3 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... |
|
Solution |
WAS 4.0
Base ORB:
- com.ibm.rmi
- com.ibm.org.omg.CORBA
ORB Extensions:
- com.ibm.CORBA.iiop
- com.ibm.CORBA.services
WAS 5.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
|
|
|
|
|
|
|