19.4.4 List of content codes

The specified timeout value is invalid.

Check the timeout value specified in the EJB client and J2EE server, and specify the predefined monitoring time.

[CORBA method]

A CORBA::BAD_PARAM exception report was received.

An attempt to allocate memory failed.

[Invoke an EJB method]

The processing of the EJB method might be complete.

[Invoke another system-provided method]

The processing of the system-provided method might be complete.

[Terminate the processing]

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

An attempt to allocate memory in the part indicated by the place code failed. Terminate the CTM system. When the CTM system terminates, change the maximum user memory size that can be allocated to each process or to the entire system, and then restart the system.

[CORBA method]

A CORBA::NO_MEMORY exception report was received.

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.

[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.

[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.

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

[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?

[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.

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

[Invoke an EJB method]

Re-invoke the EJB object. However, the previous invocation of the EJB method might be complete.

[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.

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.

Check whether the CTM regulator and OTM gateway are running.

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

[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.

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.

[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.

There was a version mismatch in the CTM communication protocol.

[Terminate the processing]

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

Check whether there is a version mismatch in the CTM programs included in the same CTM domain.

[Invoke an EJB method]

There is a version mismatch in some CTM functionality, so the processing cannot be executed.

[Terminate the processing]

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

For some functionality, the version of the process indicated in the place code does not match with another process version. Check the versions.

A timeout occurred while a J2EE application was being started.

Review, and if necessary revise, the value of ejbserver.ctm.ActivateTimeOut, and then restart the J2EE server.

A timeout occurred while a J2EE application was being stopped.

Check whether PRF is running in order to meet the completion of the EJB business request.

[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.

A timeout occurred while an ORB gateway was being started.

Start the ORB gateway before you start the J2EE application.

A timeout occurred while an ORB gateway was being terminated.

Do not start or stop multiple ORB gateways at the same time.

A timeout occurred while a J2EE application was being started.

[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.

A timeout occurred while a J2EE application was being stopped.

[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.

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.

[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.

Registration or deletion to the CORBA naming service failed.

[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.

[CORBA method]

A CORBA::COMM_FAILURE exception report was received.

The possible causes are as follows:

• A service provided by the EJB object is locked.

• The J2EE server terminated abnormally.

[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.

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.

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

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from starting the J2EE server.

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

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from restarting the CTM regulator or OTM gateway.

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

[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.

[Restart a CTM daemon]

Restart the CTM daemon, and then re-execute the operations from the JNDI Lookup processing.

A J2EE server was started while a CTM daemon was being started.

[Check the CTM daemon]

Check whether the CTM daemon is running, and then restart the J2EE server.

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

[Check the CTM daemon]

Check whether the CTM daemon is running, and then restart the CTM regulator or OTM gateway.

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

[Restart]

Start the J2EE application and CTM daemon on the same host.

The functionality is not supported.

[EJB home create]

A method other than create was issued for EJB home of a stateless session Bean.

[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.

[Other than above]

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

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

Restart the J2EE application or J2EE server after the CTM daemon starts.

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

Terminate the J2EE application or J2EE server before terminating the CTM daemon.

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

Terminate the ORB gateway before terminating the CTM daemon.

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

[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.

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

[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.

The specified CTM queue is already active.

[Terminate a J2EE server]

The CTM queue cannot be locked normally during the J2EE application stop processing. Terminate and then restart the J2EE server.

An un-shareable schedule queue has been activated.

[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.

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

[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.

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

[Re-execute the job]

Change the job ID specified in the cjexecjob (batch application execution) command, and then re-execute the cjexecjob command.

[CORBA method]

A CORBA::NO_PERMISSION exception report was received.

An error occurred during the parsing of a property definition.

[Terminate the processing]

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

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

An error occurred during the processing of a communication protocol.

[Terminate the processing]

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

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

An error occurred during exclusive control processing.

[Terminate the processing]

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

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.

An error occurred during communication between threads with exclusive control.

[Terminate the processing]

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

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.

An error occurred during communication between threads.

[Terminate the processing]

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

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.

An error occurred during the initialization of shared memory.

[Terminate the processing]

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

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.

An error occurred while a thread was being generated.

[Terminate the processing]

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

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.

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

[Terminate the processing]

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

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.

An attempt to acquire the connection identifier failed.

[Terminate the processing]

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

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.

[CORBA method]

A CORBA::INTERNAL exception report was received.

Another error occurred in the CTM system.

[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.

Acquire the content code, place code, completed status, and maintenance code 1 to 4, and then contact the System Administrator.

[CORBA method]

A CORBA::MARSHAL exception report was received.

An attempt to read a shared library failed.

Check whether the library path environment variable has been set up correctly.

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

Specify a predefined CTM identifier (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMID.

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

Specify a predefined CTM domain name (1 to 31 alphanumeric characters) in the property ejbserver.ctm.CTMDomain.

The CTMDIR environment variable or CTMSPOOL environment variable is invalid.

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.

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

Specify the predefined host name or IP address (string of 1 to 64 characters) in the property ejbserver.ctm.CTMMyHost.

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

[Restart a J2EE server]

Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

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

[Restart a J2EE server]

Check the timeout value specified in the property, specify the predefined monitoring time, and then restart the J2EE server.

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

Review, and if necessary revise, the length of the CTM queue specified in the J2EE server property, and specify the predefined CTM queue length.

[CORBA method]

A CORBA::INITIALIZE exception report was received.

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.

[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.

[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

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.

[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.

Start the EJB object with the applicable interface name and INS registration name, and then re-execute the processing to invoke the EJB method.

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.

[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.

[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.

[CORBA method]

A CORBA::NO_IMPLEMENT exception report was received.

[CORBA method]

A CORBA::BAD_OPERATION exception report was received.

[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.

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMClientConnectCount, and then restart.

[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.

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMServerConnectCount, and then restart.

[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.

[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.

[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.

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option arguments -CTMQueueCount or -CTMQueueRegistCount, and then restart.

[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.

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.

[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.

[Change the definition]

Terminate the CTM daemon, then increase the value of the command option argument -CTMDispatchParallelCount, and then restart.

[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.

[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.

[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.

[CORBA method]

A CORBA::NO_RESOURCES exception report was received.

[Invoke an EJB method]

The response of the EJB object user method invocation did not return even after the monitoring time was exceeded. The EJB object user method invocation might be complete.

The batch application requests standing by in the schedule queue were not executed by the cjkilljob (stop batch application or forcibly stop batch server) command.

[CORBA method]

A CORBA::NO_RESPONSE exception report was received.

[Start a J2EE application]

The J2EE application is already running and the CTM queue has been activated.

[Terminate a J2EE server]

The CTM queue cannot be locked normally during the J2EE application stop processing. Terminate and then restart the J2EE server.

A J2EE application with the same CTM queue name has already been registered.

[Change the CTM queue name]

The CTM queue name of the J2EE application must be unique in the J2EE server.

[CORBA method]

A CORBA::BAD_INV_ORDER exception report was received.

[CORBA method]

A CORBA::TRANSIENT exception report was received.

[CORBA method]

A CORBA::OBJECT_NOT_EXIST exception report was received.

[CORBA method]

A CORBA::UNKNOWN exception report was received.

[CORBA method]

A CORBA::INV_OBJREF exception report was received.

[CORBA method]

A CORBA::IMPLIMIT exception report was received.

[CORBA method]

A CORBA::BAD_TYPECODE exception report was received.

[CORBA method]

A CORBA::PERSIST_STORE exception report was received.

[CORBA method]

A CORBA::FREE_MEM exception report was received.

[CORBA method]

A CORBA::INV_IDENT exception report was received.

[CORBA method]

A CORBA::INV_FLAG exception report was received.

[CORBA method]

A CORBA::INTF_REPOS exception report was received.

[CORBA method]

A CORBA::BAD_CONTEXT exception report was received.

[CORBA method]

A CORBA::OBJ_ADAPTER exception report was received.

[CORBA method]

A CORBA::DATA_CONVERSION exception report was received.

[CORBA method]

A CORBA::TRANSACTION_REQUIRED exception report was received.

[CORBA method]

A CORBA::TRANSACTION_ROLLEDBACK exception report was received.

[CORBA method]

A CORBA::INVALID_TRANSACTION exception report was received.

[CORBA method]

A CORBA::INV_POLICY exception report was received.

[CORBA method]

A CORBA::CODESET_INCOMPATIBLE exception report was received.

[CORBA method]

A CORBA::REBIND exception report was received.

[CORBA method]

A CORBA::TIMEOUT exception report was received.

[CORBA method]

A CORBA::TRANSACTION_UNAVAILABLE exception report was received.

[CORBA method]

A CORBA::TRANSACTION_MODE exception report was received.

[CORBA method]

A CORBA::BAD_QOS exception report was received.