User guide

2-38
Cisco Transport Manager Release 9.2 GateWay/CORBA User Guide and Programmer Manual
OL-20937-01
Chapter 2 NE- and CTM-Specific Details
2.2.6 Programming Details
2.2.6.3 Development Environment
CTM GateWay/CORBA has been developed with Java Development Kit (JDK) 1.54.2 and
jacORB 2.x1.3.7 on Sun Solaris 10 and is compliant with the CORBA 2.3 specification. The OSS can
use Java or the C++ IDL compiler to compile IDL files.
Note If you use Java and jacORB, the CTM server installation provides JAR files for notification IDLs and
TMF IDLs.
The thread_pool_max property indicates the maximum number of concurrent threads that CTM can
handle. By default, the thread_pool_max property is set to 200 in the
/CTM-installation-directory/bin/jcorbagw.sh file. If the value is exceeded, the following exception is
returned:
org.omg.CORBA.TRANSIENT: Server-side Exception: resource limit reached
2.2.6.4 Exception Handling
All interfaces that CTM GateWay/CORBA implements raise the exception
globaldefs::ProcessingFailureException. The following sections discuss each exception type in detail.
2.2.6.4.1 EXCPT_NOT_IMPLEMENTED
This exception indicates whether some IDL operations are optional or are not implemented in this
release. If the operation itself is not supported, the errorReason is an empty string.
2.2.6.4.2 EXCPT_INTERNAL_ERROR
This exception indicates an internal EMS error and applies to all methods.
2.2.6.4.3 EXCPT_INVALID_INPUT
This exception indicates an incorrect parameter format, such as a three-level naming attribute TP name
that is passed as a single-level name. If a parameter is out of range, this exception is also used. The reason
field contains the incorrect parameter.
2.2.6.4.4 EXCPT_ENTITY_NOT_FOUND
This exception indicates that the NMS supplied an object name as a parameter and the EMS cannot find
an object with that name. The reason field contains the name that was passed as a parameter.
2.2.6.4.5 EXCPT_UNABLE_TO_COMPLY
This exception is used as a generic value when the server cannot respond to the request.
2.2.6.4.6 EXCPT_NE_COMM_LOSS
This exception is used as a generic value when the server cannot communicate with the NE, preventing
the successful completion of the operation. All operations that involve communication with the NE
might return this exception type.