List of content codes

3004 SEND_CLNT_FAILURE

Error contents: An error occurred in the communication between the CTM regulator or OTM gateway and the CTM daemon. However, the invocation of the EJB method might be complete.

Action to be taken during development: [Invoke an EJB method]; The connection from the CTM regulator or OTM gateway to the CTM daemon might be closed. Re-execute the operations from the EJB home create processing.

Action to be taken during operations: [Restart the CTM regulator]; Make sure that the CTM daemon is running, and then restart the CTM regulator.; [Restart the OTM gateway]; Make sure that the CTM daemon is running, and then restart the OTM gateway.

3006 SEND_SERV_FAILURE

Error contents: An error occurred in the communication between the CTM daemon and J2EE server. However, the invocation of the EJB method might be complete.

Action to be taken during development

[Invoke an EJB method]

Re-invoke the EJB object. However, the previous invocation of the EJB method might be complete. Check the following items as well in the case of OTM invocation:

Is the JNDI lookup name specified while creating the TSC proxy?
Has the session been invoked?

Action to be taken during operations: [Restart a J2EE server]; Make sure that the CTM daemon is running, and then restart the J2EE server. Note that in a system executing batch applications, the J2EE server is replaced by the batch server.

3007 SEND_DAEMON_FAILURE

Error contents: An error occurred in the communication between the CTM daemons. However, the invocation of the EJB method might be complete.

Action to be taken during development: [Invoke an EJB method]; Re-invoke the EJB object. However, the previous invocation of the EJB method might be complete.

Action to be taken during operations: [Check the CTM daemon]; Make sure that the CTM daemons from the same CTM domain are running. If the CTM daemons are not running, start the CORBA naming service, then restart the CTM daemons, and then invoke the EJB method.

3008 SEND_REPLY_FAILURE

Error contents: An error occurred in the communication from the CTM daemon to the CTM regulator, ORB gateway, or OTM gateway. However, the invocation of the EJB application might be complete.

Action to be taken during operations: Check whether the CTM regulator and OTM gateway are running.

3009 BASIC_CONN_FAILURE

Error contents: The CTM daemon could not be found at the communication destination.

Action to be taken during operations: [Check osagent]; Check whether osagent is running.; [Check the environment variables]; Check whether the OSAGENT_PORT environment variable in osagent, CTM processes, and J2EE server are matching.; [Check the CTM daemon]; Check whether the CTM daemon to be connected to is running.; [Other]; Check the value specified in the ejbserver.ctm.CTMDomain or ejbserver.ctm.CTMID properties of the J2EE server.

3010 CONN_FAILURE

Error contents: An attempt to connect to the communication route failed.; [Start a J2EE server]; An error occurred in the process of connecting the J2EE server and CTM daemon.; [Start a CTM regulator]; An error occurred in the process of connecting the CTM regulator and CTM daemon.; [Start an OTM gateway]; An error occurred in the process of connecting the OTM gateway and CTM daemon.; [Start a J2EE application]; A communication error occurred in the process of activating the CTM queue.; [Stop a J2EE application]; A communication error occurred in the process of locking (deactivation) the CTM queue.; [Terminate a J2EE server]; An error occurred in the process of disconnecting the J2EE server and CTM daemon.; [Terminate a CTM regulator]; An error occurred in the process of disconnecting the CTM regulator and CTM daemon.

Action to be taken during operations: [Check the maximum number of connections (number of file descriptors)]; An attempt was made to establish connections exceeding the maximum number of connections that can be established, or the number of file descriptors that can be acquired for each process. Terminate the CTM system. Then, change the upper limit for the maximum number of connections that can be established, or the number of file descriptors that can be acquired for each process, and then restart the system.; [Check the CTM daemon]; If this exception occurs while a J2EE application is being stopped, the J2EE application cannot be started because the locking of the CTM queue is not complete. Terminate the J2EE server, make sure that the CTM daemon is running, and then restart the J2EE server.

3011 INCOMPATIBLE_PROTOCOL

Error contents: There was a version mismatch in the CTM communication protocol.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: Check whether there is a version mismatch in the CTM programs included in the same CTM domain.

3012 NOT_IGNORE_PROTOCOL

Error contents: [Invoke an EJB method]; There is a version mismatch in some CTM functionality, so the processing cannot be executed.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: For some functionality, the version of the process indicated in the place code does not match with another process version. Check the versions.

3013 ACTIVATE_TIMED_OUT

Error contents: A timeout occurred while a J2EE application was being started.

Action to be taken during operations: Review, and if necessary revise, the value of ejbserver.ctm.ActivateTimeOut, and then restart the J2EE server.

3014 DEACTIVATE_TIMED_OUT

Error contents: A timeout occurred while a J2EE application was being stopped.

Action to be taken during development: Check whether PRF is running in order to meet the completion of the EJB business request.

Action to be taken during operations: [Terminate a J2EE server]; The J2EE application cannot be started because the process of locking the CTM queue is not complete. Terminate and then restart the J2EE server.

3015 CLNT_CONN_TIMED_OUT

Error contents: A timeout occurred while an ORB gateway was being started.

Action to be taken during operations: Start the ORB gateway before you start the J2EE application.

3016 CLNT_DISCONN_TIMED_OUT

Error contents: A timeout occurred while an ORB gateway was being terminated.

Action to be taken during operations: Do not start or stop multiple ORB gateways at the same time.

3017 SERV_CONN_TIMED_OUT

Error contents: A timeout occurred while a J2EE application was being started.

Action to be taken during operations: [Restart a J2EE application]; Restart the J2EE application.; If the error occurs frequently, acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

3018 SERV_DISCONN_TIMED_OUT

Error contents: A timeout occurred while a J2EE application was being stopped.

Action to be taken during operations: [Restart a CTM daemon]; Restart the CTM daemon.; If the error occurs frequently, acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

3021 DEACTIVATE_FAILURE

Error contents

An error occurred while a J2EE application was being stopped. The possible causes are as follows:

Normal lock processing cannot be executed while the J2EE application is running.
A communication error occurred in the CTM daemon during communication.
A timeout was detected in the CTM daemon during communication.

Action to be taken during operations: [Terminate a J2EE server]; For details on the error, see the message KFCT75122-E. The J2EE application cannot be started because the process of locking the CTM queue is not complete. Terminate and then restart the J2EE server.

3022 SEND_INS_FAILURE

Error contents: Registration or deletion to the CORBA naming service failed.

Action to be taken during operations: [Check the CORBA naming service]; Make sure that the CORBA naming service is running, and then restart the J2EE application.; If the information for the CORBA naming service is inconsistent, the J2EE application cannot be started. Terminate the COBRA naming service and CTM daemon, and re-execute the operations from starting the COBRA naming service.

3998 TPBROKER_COMM_FAILURE

Error contents: [CORBA method]; A CORBA::COMM_FAILURE exception report was received.

(4) Content codes from 4000 to 4999

4001 CALL_IN_HOLD

Error contents

The possible causes are as follows:

A service provided by the EJB object is locked.
The J2EE server terminated abnormally.

Action to be taken during development: [Retry (when unlock can be executed)]; Re-invoke the EJB method.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: If the services provided by the EJB object are locked, unlock those services, and then re-invoke the EJB method.; If the J2EE server terminated abnormally, restart the J2EE server as and when required, and then re-invoke the EJB method.

4005 SERV_CONN_IN_END

Error contents: A J2EE server was started while a CTM daemon was being terminated.

Action to be taken during operations: [Restart a CTM daemon]; Restart the CTM daemon, and then re-execute the operations from starting the J2EE server.

4007 CLNT_CONN_IN_END

Error contents: A CTM regulator or OTM gateway was started while a CTM daemon was being terminated.

Action to be taken during operations: [Restart a CTM daemon]; Restart the CTM daemon, and then re-execute the operations from restarting the CTM regulator or OTM gateway.

4009 CALL_IN_END

Error contents: An EJB object was invoked while a CTM daemon was being terminated. The invocation of the EJB method was not completed.

Action to be taken during development: [Retry (CORBA naming service)]; To search for another CTM daemon, re-execute the operations from the JNDI Lookup processing.

[Terminate the processing]: Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: [Restart a CTM daemon]; Restart the CTM daemon, and then re-execute the operations from the JNDI Lookup processing.

4011 SERV_CONN_IN_START

Error contents: A J2EE server was started while a CTM daemon was being started.

Action to be taken during operations: [Check the CTM daemon]; Check whether the CTM daemon is running, and then restart the J2EE server.

4012 CLNT_CONN_IN_START

Error contents: A CTM regulator or OTM gateway was started while a CTM daemon was being started.

Action to be taken during operations: [Check the CTM daemon]; Check whether the CTM daemon is running, and then restart the CTM regulator or OTM gateway.

4013 CTMD_IS_NOT_MY_HOST

Error contents: The J2EE application was started on a host different from the CTM daemon.

Action to be taken during operations: [Restart]; Start the J2EE application and CTM daemon on the same host.

4015 NOT_SUPPORTED

Error contents: The functionality is not supported.; [EJB home create]; A method other than create was issued for EJB home of a stateless session Bean.

Action to be taken during development: [Retry (EJB home create)]; Check whether a method other than create was issued for EJB home, and then re-execute the operation.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: [Other than above]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

4016 ACTIVATE_IN_START

Error contents: The processing to start a J2EE application was executed while a CTM daemon was being started.

Action to be taken during operations: Restart the J2EE application or J2EE server after the CTM daemon starts.

4018 DEACTIVATE_IN_END

Error contents: The processing to stop a J2EE application was executed while a CTM daemon was being terminated.

Action to be taken during operations: Terminate the J2EE application or J2EE server before terminating the CTM daemon.

4020 CLNT_DISCONN_IN_END

Error contents: An attempt was made to terminate an ORB gateway while a CTM daemon was being terminated.

Action to be taken during operations: Terminate the ORB gateway before terminating the CTM daemon.

4022 ACTIVATE_WITH_DIFF_PROP

Error contents: The types of EJB objects provided by the J2EE applications registered with the same CTM queue name do not match.

Action to be taken during development: [Check the J2EE application]; When changing the CTM queue name, or when sharing the CTM queue, match the types of the EJB objects to be registered in the J2EE application.

4035 INVALID_NAME_PAIR

Error contents: The combination of the INS registration name and the interface name differs from the combination that is already registered.

Action to be taken during development: [Change the definition of the J2EE application]; Check the combination of the EJB object interface name and INS registration name that is registered in the J2EE application, and then restart the J2EE application.

4037 QUEUE_IS_ACTIVE

Error contents: The specified CTM queue is already active.

Action to be taken during operations: [Terminate a J2EE server]; The CTM queue cannot be locked normally during the J2EE application stop processing. Terminate and then restart the J2EE server.

4039 ACTIVATE_WITH_UNMATCH_QUEUE

Error contents: An un-shareable schedule queue has been activated.

Action to be taken during operations: [Check the schedule queue]; When changing the CTM queue name, or when sharing the schedule queue, match the types of the schedule queues to be activated.

4040 CALL_IN_BATCH_QUEUE

Error contents: Only batch server requests can be registered in the batch schedule queue.

Action to be taken during operations: [Start a J2EE application]; Start a J2EE application that provides a schedule queue that can receive requests, and then re-execute the processing to invoke the user method of the EJB object.

4041 INVALID_JOB_ID

Error contents: The job ID of the received batch application is already in use.

Action to be taken during operations: [Re-execute the job]; Change the job ID specified in the cjexecjob (batch application execution) command, and then re-execute the cjexecjob command.

4998 TPBROKER_NO_PERMISSION

Error contents: [CORBA method]; A CORBA::NO_PERMISSION exception report was received.

(5) Content codes from 5000 to 5999

5001 PROPERTIES_FAILURE

Error contents: An error occurred during the parsing of a property definition.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

5002 MSG_TYPE_FAILURE

Error contents: An error occurred during the processing of a communication protocol.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

5003 MUTEX_FAILURE

Error contents: An error occurred during exclusive control processing.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5004 SIG_COND_FAILURE

Error contents: An error occurred during communication between threads with exclusive control.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5005 EVENT_FAILURE

Error contents: An error occurred during communication between threads.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5006 SH_MEM_FAILURE

Error contents: An error occurred during the initialization of shared memory.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: Check whether the relationship between the CTMSPOOL environment variable and CTM domain name is correct. Also, check whether the value specified for the -CTMServerCacheSize option argument in the ctmstart command is correct.

5007 THREAD_CREATE_FAILURE

Error contents: An error occurred while a thread was being generated.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: An attempt was made to generate threads exceeding the maximum number of threads for a process. Increase the maximum number of threads for a process.

5008 TSD_FAILURE

Error contents: An error occurred during the initialization of thread-specific memory.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5011 CONN_INFO_FAILURE

Error contents: An attempt to acquire the connection identifier failed.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: The memory might be insufficient in the part indicated in the place code. Terminate the CTM system. Then increase the maximum user memory size for each process, and then restart the system.

5998 TPBROKER_INTERNAL

Error contents: [CORBA method]; A CORBA::INTERNAL exception report was received.

5999 PROGRAM_ERROR

Error contents: Another error occurred in the CTM system.

Action to be taken during development: [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing. Also, terminate the EJB client application or J2EE server processes.

Action to be taken during operations: Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

(6) Content codes from 6000 to 6999

(7) Content codes from 7000 to 7999

7005 LOAD_SHLIB_FAILURE

Error contents: An attempt to read a shared library failed.

Action to be taken during operations: Check whether the library path environment variable has been set up correctly.

7006 INVALID_DEF_CTMID

Error contents: The CTM identifier specified in the property ejbserver.ctm.CTMID is invalid.

Action to be taken during operations: Specify a predefined CTM identifier (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMID.

7007 INVALID_DEF_DOMAIN_NAME

Error contents: The CTM domain name specified in the property ejbserver.ctm.CTMDomain is invalid.

Action to be taken during operations: Specify a predefined CTM domain name (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMDomain.

7009 INVALID_ENV_CTMDIR

Error contents: The CTMDIR environment variable or CTMSPOOL environment variable is invalid.

Action to be taken during operations: In the CTMDIR environment variable, specify the directory in which CTM is installed, or check whether the CTMSPOOL directory exists and the user has permission to access the directory.

7020 INVALID_DEF_MY_HOST

Error contents: The host name or IP address specified in the property ejbserver.ctm.CTMMyHost is invalid.

Action to be taken during operations: Specify the predefined host name or IP address (string of 1 to 64 characters) in the property ejbserver.ctm.CTMMyHost.

7032 INVALID_DEF_ACTIVATE_TIMEOUT

Error contents: The value specified in the property (ejbserver.ctm.ActivateTimeOut) that sets the activation timeout value for the J2EE application, is invalid.

Action to be taken during operations: [Restart a J2EE server]; Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

7033 INVALID_DEF_DEACTIVATE_TIMEOUT

Error contents: The value specified in the property (ejbserver.ctm.DeactivateTimeOut) that sets the deactivation timeout value for the J2EE application, is invalid.

Action to be taken during operations: [Restart a J2EE server]; Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

7040 INVALID_DEF_QUEUE_LENGTH

Error contents: The length of the CTM queue specified in the property ejbserver.ctm.QueueLength is invalid.

Action to be taken during operations: Review, and if necessary revise, the length of the CTM queue specified in the J2EE server property, and specify the predefined CTM queue length.

7998 TPBROKER_INITIALIZE

Error contents: [CORBA method]; A CORBA::INITIALIZE exception report was received.

(8) Content codes from 8000 to 8999

8001 NO_SUCH_INTERF

Error contents: EJB home or EJB object was invoked from the client, but the J2EE application has not been started. Therefore, the EJB object could not be invoked.

Action to be taken during development: [Retry (invoke an EJB method)]; Start the J2EE application that provides the EJB object for the applicable interface, and then re-invoke the EJB object.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations

[Start a J2EE application]

Start the J2EE application that provides the EJB object for the applicable interface, and then re-execute the processing to invoke the EJB object user method.

[Check the environment settings]

Check whether the CTM domain manager environment settings are incorrect, and then re-invoke the EJB object. The following environment settings might be incorrect:

Value specified in the OSAGENT_PORT environment variable
Value specified in the command option argument -CTMDomain
Value specified in the command option argument -CTMPort
Value specified in the command option argument -CTMSendInterval

8002 NO_SUCH_NAME

Error contents: An EJB object was invoked from the client, but a J2EE application providing an EJB object with the same interface name and same INS registration name has not been started. Therefore, the EJB object could not be invoked.

Action to be taken during development: [Retry (invoke an EJB method)]; Start the J2EE application that provides the EJB object with the applicable interface name and INS registration name, and then re-invoke the EJB object.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations: Start the EJB object with the applicable interface name and INS registration name, and then re-execute the processing to invoke the EJB method.

8003 NO_SUCH_REGLTD

Error contents: An EJB object was invoked from the client, but the CTM regulator is not running in the CTM daemon that started the J2EE application. Therefore, the EJB object could not be invoked.

Action to be taken during development: [Retry (EJB home create)]; Start the CTM regulator and J2EE server in the CTM daemon that starts the J2EE application, and then re-invoke the create method for EJB home.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate the invocation of the EJB object.

Action to be taken during operations: [Check the CTM regulator]; Check whether the CTM regulator is running in the CTM daemon that started the J2EE application. If the CTM regulator is not running, start the CTM regulator, and then re-execute the processing to invoke the EJB method.

8998 TPBROKER_NO_IMPLEMENT

Error contents: [CORBA method]; A CORBA::NO_IMPLEMENT exception report was received.

(9) Content codes from 9000 to 9999

(10) Content codes from 10000 to 10999

10001 OVER_MAX_CLNT

Error contents: [Start a CTM regulator]; The number of CTM regulators exceeds the value specified in the command option argument -CTMClientConnectCount of the CTM daemon.; [Start an OTM gateway]; The number of OTM gateways exceeds the value specified in the command option argument -CTMClientConnectCount of the CTM daemon.

Action to be taken during operations: [Change the definition]; Terminate the CTM daemon, then increase the value of the command option argument -CTMClientConnectCount, and then restart.

10002 OVER_MAX_SERV

Error contents: [Start a J2EE server]; The number of J2EE servers connected to the CTM daemon exceeds the value specified in the command option argument -CTMServerConnectCount of the CTM daemon.

Action to be taken during operations: [Change the definition]; Terminate the CTM daemon, then increase the value of the command option argument -CTMServerConnectCount, and then restart.

10006 OVER_ADM_MAX_SERV

Error contents: [Start a J2EE server]; The number of processes managed by the CTM daemon exceeds the value specified in the command option argument -CTMEntryCount of the CTM daemon.

Action to be taken during operations: [Change the definition]; Terminate the CTM daemon, then increase the value of the command option argument -CTMEntryCount (-CTMServerConnectCount if the value is omitted), and then restart.

10007 OVER_MAX_QUEUE

Error contents: [Start a J2EE application]; The number of CTM queues registered in the CTM daemon exceeds the value specified in the command option arguments -CTMQueueCount or -CTMQueueRegistCount of the CTM daemon.

Action to be taken during operations: [Change the definition]; Terminate the CTM daemon, then increase the value of the command option arguments -CTMQueueCount or -CTMQueueRegistCount, and then restart.

10008 OVER_MAX_THIN_CLIENT

Error contents: [Invoke an EJB method]; The number of clients connected to the CTM regulator, ORB gateway, or OTM gateway exceeds the value specified in the -CTMClientConnectCount option argument.

Action to be taken during operations: Increase the number of CTM regulator, ORB gateway, or OTM gateway processes, or review, and if necessary revise, the value specified in the -CTMClientConnectCount option, and then restart.

10009 OVER_MAX_DISPATCH_PARALLEL

Error contents: [Start a J2EE application]; The total parallel count of the CTM queues registered in the CTM daemon (number of resident threads) exceeds the value specified in command option argument -CTMDispatchParallelCount of the CTM daemon.

Action to be taken during operations: [Change the definition]; Terminate the CTM daemon, then increase the value of the command option argument -CTMDispatchParallelCount, and then restart.

10010 OVER_MAX_REQUEST_COUNT

Error contents: [Invoke an EJB method]; The maximum number of schedule queues for the J2EE applications providing the EJB objects of the interfaces invoked from the client was exceeded.

Action to be taken during development: [Retry]; Re-invoke the EJB object. The schedule queue might be empty.; If this error occurs continuously for a long time, increase the parallel count of the J2EE applications providing the EJB objects of that interface, or increase the number of J2EE server processes.; [Terminate the processing]; Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then terminate CTM processing.

Action to be taken during operations: [Change the definition]; Increase the J2EE applications containing the same EJB object as the applicable interface name, or increase the J2EE application parallel count, and then restart the J2EE application.

10998 TPBROKER_NO_RESOURCES

Error contents: [CORBA method]; A CORBA::NO_RESOURCES exception report was received.

(11) Content codes from 11000 to 11999

(12) Content codes from 12000 to 12999

(13) 13000 and subsequent content codes

13998 TPBROKER_TRANSIENT

Error contents: [CORBA method]; A CORBA::TRANSIENT exception report was received.

14998 TPBROKER_OBJECT_NOT_EXIST

Error contents: [CORBA method]; A CORBA::OBJECT_NOT_EXIST exception report was received.

15998 TPBROKER_UNKNOWN

Error contents: [CORBA method]; A CORBA::UNKNOWN exception report was received.

16998 TPBROKER_INV_OBJREF

Error contents: [CORBA method]; A CORBA::INV_OBJREF exception report was received.

17998 TPBROKER_IMP_LIMIT

Error contents: [CORBA method]; A CORBA::IMPLIMIT exception report was received.

18998 TPBROKER_BAD_TYPECODE

Error contents: [CORBA method]; A CORBA::BAD_TYPECODE exception report was received.

19998 TPBROKER_PERSIST_STORE

Error contents: [CORBA method]; A CORBA::PERSIST_STORE exception report was received.

20998 TPBROKER_FREE_MEM

Error contents: [CORBA method]; A CORBA::FREE_MEM exception report was received.

21998 TPBROKER_INV_IDENT

Error contents: [CORBA method]; A CORBA::INV_IDENT exception report was received.

22998 TPBROKER_INV_FLAG

Error contents: [CORBA method]; A CORBA::INV_FLAG exception report was received.

23998 TPBROKER_INTF_REPOS

Error contents: [CORBA method]; A CORBA::INTF_REPOS exception report was received.

24998 TPBROKER_BAD_CONTEXT

Error contents: [CORBA method]; A CORBA::BAD_CONTEXT exception report was received.

25998 TPBROKER_OBJ_ADAPTER

Error contents: [CORBA method]; A CORBA::OBJ_ADAPTER exception report was received.

26998 TPBROKER_DATA_CONVERSION

Error contents: [CORBA method]; A CORBA::DATA_CONVERSION exception report was received.

27998 TPBROKER_ TRANSACTION_REQUIRED

Error contents: [CORBA method]; A CORBA::TRANSACTION_REQUIRED exception report was received.

28998 TPBROKER_ TRANSACTION_ROLLEDBACK

Error contents: [CORBA method]; A CORBA::TRANSACTION_ROLLEDBACK exception report was received.

29998 TPBROKER_ INVALID_TRANSACTION

Error contents: [CORBA method]; A CORBA::INVALID_TRANSACTION exception report was received.

30998 TPBROKER_ INV_POLICY

Error contents: [CORBA method]; A CORBA::INV_POLICY exception report was received.

31998 TPBROKER_ CODESET_INCOMPATIBLE

Error contents: [CORBA method]; A CORBA::CODESET_INCOMPATIBLE exception report was received.

32998 TPBROKER_ REBIND

Error contents: [CORBA method]; A CORBA::REBIND exception report was received.

33998 TPBROKER_ TIMEOUT

Error contents: [CORBA method]; A CORBA::TIMEOUT exception report was received.

34998 TPBROKER_ TRANSACTION_UNAVAILABLE

Error contents: [CORBA method]; A CORBA::TRANSACTION_UNAVAILABLE exception report was received.

35998 TPBROKER_ TRANSACTION_MODE

Error contents: [CORBA method]; A CORBA::TRANSACTION_MODE exception report was received.

36998 TPBROKER_ BAD_QOS

Error contents: [CORBA method]; A CORBA::BAD_QOS exception report was received.

19.4.4 List of content codes

(1) Content codes from 1000 to 1999

(2) Content codes from 2000 to 2999

(3) Content codes from 3000 to 3999